SatMods.com - FTA - FTA Files - FTA Bin - FTA Keys - FTA Forums  

Maritime-fta



Upgrade Your Account To ViP To Support SatMods + Get Priority Access & Support!

Go Back   SatMods.com - FTA - FTA Files - FTA Bin - FTA Keys - FTA Forums > Receiver Forums > Neusat - Neosat > Neusat - Neosat Discussion


Complete history of Neosat iPro 1000/2000 and nFusion.

Neusat - Neosat Discussion Thread, Complete history of Neosat iPro 1000/2000 and nFusion. in Neusat - Neosat; Complete history of Neosat iPro 1000/2000 and nFusion. So many people have not been around since the beginning and don't ...

Closed Thread
 
LinkBack Thread Tools Display Modes
  #1  
Old 06-19-2009, 12:27 AM
MOD's Avatar
MOD MOD is offline
 
Join Date: Sep 2008
Posts: 5,074
Default Complete history of Neosat iPro 1000/2000 and nFusion.

Complete history of Neosat iPro 1000/2000 and nFusion.


So many people have not been around since the beginning and don't know the history of the Neosat iPro 1000/2000 and the nFusion.

Here is how it all unfolded:

1). Dr. T was the only coder in the NORW group. The NORW group was coding for Coolsat.

2). The NORW group wanted to produce the Neosat iPro 1000 and v2neo came on board to setup IKS for the iPro 1000. Keep in mind that the manufacturer's coders are the ones actually releasing the .BINs. Dr. T and v2neo are mostly coding the IKS portion and do not have the full source code for the iPro 1000.

3). Blindscam/Matchstick in the NORW group wanted to screw over the Neosat people by introducing his own nFusion STB. He was greedy and wanted to keep more money for himself. He convinced the manufacturer that was making the iPro 1000 and the nFusion to stop releasing .BINs for the iPro 1000.

4). Dr. T disagreed with Blindscam and left the NORW group to form the v2group with v2neo. The iPro 1000 server is controlled by the nFusion manufacturer. The nFusion manufacturer locks out all iPro 1000 users from the IKS server. The nFusion manufacturer and the nFusion group are obviously not very bright. Anyone who buys any STB made by the nFusion manufacturer is not thinking clearly. They will burn you in the future. They have proven that they are greedy and will drop support in order to try to force you to upgrade to their newest STB.

5). Dr. T and v2neo come out with the Neosat iPro 2000. Much discussion was held about changing the name. They knew that the manufacturer dropping support for the Neosat iPro 1000 could reflect negatively on the new Neosat iPro 2000 even though it is made by a completely different manufacturer. In the end, it was decided that the name Neosat would carry more weight than some new unknown name.

6). IKS on the iPro 2000 had to be developed from scratch. The nFusion group being in bed with the manufacturer had access to the IKS system that was perfected by v2neo and Dr. T.

7). The Neosat iPro 2000 is far superior to the nFusion. The nFusion is just the old iPro 1000 with a different tuner and 16Mb of RAM instead of the iPro's 8Mb of RAM. The iPro 2000 has 64Mb of RAM.

8). HIKS is far superior to the old IKS that was developed by v2neo and Dr. T. Once HIKS is released there won't be any comparison between nFusion's old iPro 1000 technology and the new iPro 2000.

9). The v2group can not support the old iPro 1000. In order to force the nFusion manufacturer to release .BINs for the iPro 1000, v2neo threatened to release what source code they had for the iPro 1000 into the public domain. To stop that from happening, the nFusion manufacturer agreed to release Bluejay .BINs that would run on the iPro 1000. As long as the iPro 1000 gets a new .BIN when the Bluejay gets one, the v2group, by agreement, is not allowed to support the iPro 1000. Interestingly, at this point, it appears that the nFusion manufacturer has decided to drop support on ALL of the STBs that can run a Bluejay .BIN: Tessat, Satcruiser, Bluejay, Neosat iPro 1000, Neosat Lite, etc. Unfortunately, this still means that the v2group can not support the iPro 1000. If the Bluejay ever gets a .BIN and the iPro 1000 does not, then the v2group could either support the iPro 1000 or release what source code they have.

There you have it. A greedy nFusion group and a greedy manufacturer have caused all of this conFusion and set back the development of the Neosat iPro 2000.
__________________




Testing: Sonysat DCR5500, pansat 9000hd, sv4k, sv360premier, pansat 2700a, coolsat 6000 and satopia ST1100-UT

Closed Thread

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Neosat Ipro 2000 Remote Codes MOD Neusat - Neosat Tutorials 0 06-19-2009 12:25 AM
Neosat ipro/pro How to use channel master MOD Neusat - Neosat Tutorials 0 06-19-2009 12:22 AM
Neosat/Neusat iPro 2000 IKS via (cellular connection) MOD Neusat - Neosat Tutorials 0 06-19-2009 12:21 AM
How to Upgrade Neosat IPro with 1.1(aka)3.34 MOD Neusat - Neosat Tutorials 0 06-19-2009 12:19 AM
Breaking EKS News for Neosat iPro! musky Rumors Area 0 06-07-2009 02:47 PM


Maritime-fta



All times are GMT. The time now is 10:24 PM.


Powered by vBulletin® Version 3.8.3
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
AzBox - Captiveworks - Conaxsat - Coolsat - ILink - KBox - Neosat - Nfusion - Pansat - Sonicview - SonySat - Viewsat - Visionsat - FTA - Files - BIN - HD