|
A plan to revive old Morpheus 1.3.3 and avoid KaZaA's "Upgrade Morpheus" trick
First of all, I'm new here, so I'm really sorry if my idea is not new or is known not to work - I tried to look over the forums to see if a similiar idea was tried, and I'm really sorry if I missed one and am just bothering you now :) Also, if you know I'm wrong somewhere here, please let me know.
So, as far as I understand, Sharman Networks or KaZaA BV (a.k.a FastTrack) put into v1.5 of the FastTrack core a function that will make each v1.5 superpeer to kick out old v1.3.3 users by requiring them to upgrade. This effectively kicked StreamCast's Morpheus out of the network, since StreamCast wasn't supplied with a v1.5 FastTrack core to use for an upgraded Morpheus 1.5. StreamCast then released Morpheus Preview Edition 1.3.3.1 which doens't connect to the FastTrack network anymore, but to Gnutella. After a while, users discovered that the old, FastTrack-based Moprheus 1.3.3 works again. It didn't connect to the KaZaA-Grokster-iMesh FastTrack though, but to an independent network automatically created. This network received the nickname "iMorpheus". But then after another while it again stopped working, saying it needs an upgrade (just like before). From time to time this "iMorpheus" network went up and then down again with the "upgrade" notice. The assumed explanation for this was there were neither none or very little number of v1.3.3 superpeers in the user's area, or KaZaA kept switching the "upgrade" notice sent from v1.5 users to v.1.3.3 users on and off, as Sharman Networks or KaZaA BV are suspected to have direct control over this feature. Whatever really makes the v1.3.3 clients not to connect to its own independent network, it probably won't work if there were no (or at least less then the number of v1.5 clients there are now) v1.5 clients on FastTrack, since these are the ones who keep kicking v1.3.3 users out. But even if we could convince people not to use v1.5+, what COULD they use, if v1.3.3 clients aren't working anymore? That why I did some tests. Indeed, on my computer, Morpheus 1.3.3 refuses to connect, telling me to download an upgrade which doesn't exist. I got a version of KaZaA 1.3.3 and it didn't work either, however tKaZaA 1.3.3 actually had an upgrade available (I was offered to download 1.5.1 - probably I connected to a 1.5.1 superpeer ant not to a 1.6 one). Anyways, I can't upgrade to 1.5+ 'cuz it kicks Morpheus out. So I did a little thinking. Then I remebered that just a little while before KaZaA.com was bought by Sharman Networks, FastTrack released an update to KaZaA 1.3.3 - it was called KaZaA 1.4. I think the only difference (that we were told about) was a new Recommendations system. However KaZaA.com was soon purchased, and the new owners, Sharman networks, for some reason didn't like 1.4, so they released KaZaA 1.3.4 (strange that they made a step back in the verion numbering) short after. I don't trust Sharman, so I haven't tried v1.3.4, however I DID find KaZaA 1.4 (which came out BEFORE 1.3.4 and was never officialy available again - Sharman just jumped straight to 1.5 after 1.3.4) and it works like a charm. It does ASK you if you want to upgrade, but you don't HAVE TO, and it can be used to connect to the actual FastTrack network, not just an independent one. SO what does this mean? I suspect that this 1.4 version released by FastTrack might not have the mechanism the demands older clients to upgrade, and\or that KaZaA (sharman\FastTrack) can't control it. If so, this can be used as a link between the old Morpheus 1.3.3 and the "wide" FastTrack network, or at least to fill the network with clients that KaZaA can't control. If we make users download this fast enough, there might be too many v1.4 clients before KaZaA notices them, and they would be too many to be blocked. I therefore started working on a spyware-free version. If we can make the "KaZaA Lite" websites to feature some kind of a "KaZaA Lite 1.4" and explain why this should be used and not newer versions (newer versions don't really offer anything new for the end user anyway), maybe it could get pretty popular. Please tell me what you think. Thanks! |
Some interesting thoughts and observations. I enjoyed reading your post. I am a bottom line person, and here's a boiled down prediction and answer to your question.
1) You are right, the FastTrack Network has shown to be the fastest, easiest and best p2p network to date. No other system is better right now. 2) There is no need for iMorpheus right now because the Kazaa lite program is so popular and it's loaded with users and results. (In other words, why use a IMorpheus type clone with only a few users online when the real thing has over 1.5 million online) 3) If the FastTrack network was shut down, or there was some other big disruption in the network, I would be willing to bet that someone will do exactly what you're saying. They would take an older version of Kazaa or Morpheus, change the branding, change some registry settings and it would live forever, decentralized. I think eventually #3 will happen. I also believe that FastTrack in some sort of open source way will live forever. Nick |
Newer versions keep hiding surprises. v1.5 kicked out old clients. And about v1.6? It just isn't around for enough time to show it's new hidden "features". KaZaA v1.4 isn't any different then 1.5+ for the end user. With the spyware taken out it is just as useful as "KaZaA Lite", as it connects to the whole FastTrack network with those 1.5 million users. By using a hacked v1.4, we avoid all the new surprises, enjoy the same network as with newer versions, and prepare the ground for using a working, non-hacked, spyware-free, ad-free (since the adservers no longer works) morpheus 1.3.3 comeback. If a v1.3.3 client connects to a KaZaA v1.4 superpeer, it should theoretically connect to the rest of FastTrack through it, so Morpheus could connect to the whole FastTrack network again, and not just the independent "iMorpheus"!
And even if v1.4 isn't used to get Morpheus back, I think it should still be used to give KaZaA less control and power... |
Re: A plan to revive old Morpheus 1.3.3 and avoid KaZaA's "Upgrade Morpheus" trick
Quote:
|
why this won't work...
Your idea is a good one but it won't work. Sorry.
The basic reason is that the mechanism that 1.5 used to upgrade and then force upgrade the 1.3.3 clients to 1.5 will eventually pollute your new network. I will explain in some detail so get a cup of coffee and read this slowly the first time though. You may need to think about for a few minutes to grasp the math and its logic. If you managed to say create a network of 1.3.3 or even 1.4 of say 20 active supernodes and 2500 clients the resulting structure would be a multiply linked list of computers. In simple terms each client is connected to 1 or more, or N1, N2 … Nn links where n <= 12 . I got the 12 number from some post in the Morpheus user form a long time ago. It is not important nor critical if that is the right number as long as it is at least greater then 3 for reasons I won’t explain here. Since Supernodes process FastTrack searches, the 1 to N relationship, and since each supernodes knows about S supernodes, where S > then about 12 relationship guarantees that: a) If X-1 where X> 2 supernodes go offline then the single client will still be able to search on the N1 supernode, b) If N supernodes go offline, the client is orphaned and thus has to re-login or reconnect to the network to continue searching, c) If S supernodes go offline, the supernode is orphaned and now has to log again as a client and get promoted or have a connected client tell it about another supernode so S is again greater then 1 and reconnects to the original network eventually growing back to S ~= 12. This causes each client to link like a node in a web of N connections. As long as at least one link is connected the node is still part of the web. Cut all links and the node is orphaned. So why won’t your idea work? Clients and supernodes constant talk to each other and exchange supernodes IP’s somehow. That I don’t know so don’t ask. This is the glue that binds the network together and makes it self healing. This is required because people turn off the their computers for dumb reasons. If the turned off computer is a supernode then this causes many connected client to lose an N link. If enough supernodes disconnect the network dies on that client because the client can’t search. So back to the network of 20 active nodes and 2500 clients. The network would be stable by itself. However if a 1.5 client or supernode attempts to join it will start to tell the nodes to force upgrade. Again I don’t know how but the effect has been well documented. The 1.3.3 supernodes will alter their registry as discussed in other posts to only use 1.5 after restart and won’t connect. Then the N and S links will start to fail like a wave in a pond when you throw a stone in the middle as computers are turned off and on. Another real world example is the Cellular telephone network with phones and cell sites. Go out of range of that last cell site and your phone stops working. Why? Same reason - no N links. If you want to create a 1.3.3 network again you have to make sure that you changed the port from 1214 to say 1215 to basically create an alternate network with no chance of a 1.5 node touching it. However all the fellows at FastTrack are pretty smart so to kill your new network all they have to do is modify a 1.5 client to port 1215, join your network, plant the upgrade message and shutdown. Within a short period it will shut itself down with no valid upgrade path. Morpheus was not attacked by anybody. All that noise a couple of months ago was simply basic ignorance of how the N Linked Networks actually work. Morpheus was simply denied the upgrade path by 1.5. It shut itself down as people turned off their computers. The obvious question that the attentive reader might ask is could FastTrack Va.b be shut down? Theoretically speaking yes if you understood the mechanism of the upgrade from Va.b to Va.c. However to do so would required to send the upgrade message to Y clients and supernodes, where Y > Z*2/3 with Z being the total number of nodes on the network. Unlikely to happen in real life though because Z > 20,000,000 for sure and since at least 18,500,000 are not connected at any one time you simply cannot send the forced upgrade message to Z*2/3 nodes as long a Z > 2. So why did the forced upgrade work from 1.3.3 to 1.5 and not die off? Because FastTrack V1.5 continued to operate after the upgrade and kept sending the force upgrade message achieving Z nodes messaged. So forget it, it won’t work. |
Quote:
And about KaZaA v1.4 being locked out - maybe (I have no basis to say this, just guessing) the reason Sharman Networks were so rushed to take v1.4 of the net and strangely release v1.3.4 was because they found v1.4 cannot be locked out the way they planned so they had to act fast and take it out of use? Probably not, as there could be hundreds of other reasons, but who knows. Anyways, fact is that v1.4 hasn't been locked out YET, this has gotta mean something, it is much older than v1.5 (by the rate new versions are coming out, that is)... And we know for sure that newer versions of KaZaA have more "surprises" and no real new features, then why not stick with the oldest one still working? |
Sure will work, snowman
Snowman - I understand what you're saying, and this is why v1.3.3-based "iMorpheus" keeps dying.
But this is where my "discovery" comes into place. v1.4 isn't blocked by v1.5+. And probably v1.4 doesn't block v1.3.3, as v1.3.3 wasn't blocked by it before. What does it mean? First we distribute lots of v1.4 clients. Those will have no problem connecting to the COMPLETE KaZaA-Grokster-iMesh FastTrack network, as v1.4 CAN be connected to v1.5+ superepeers and isn't locked by them. Later, when enough v1.4 clients are online, Morpheus could be used again, first connecting to v1.4 clients and later to other v1.3.3 clients, Morpheus could use v1.4 superpeers as gateways into the whole FastTrack network, and therefore will not suffer the fast death of a small "independent" network. |
be my guest; try it
It won't work because you cannot control what supernodes the 1.3.3 or 1.4 or 1.5 client connects to when it starts up.
Touch a 1.5 and it is dead by the meachnism I described above. |
1.4 clients will connect to 1.5 clients with no problem. I tested it. About 1.3.3 clients - I got the impression that before the first time it shows the upgrade notice, it tries many supernodes and shows only when it is unsuccessful. I may be wrong however.
But anyways - 1.4 clients will have no problem to connect to 1.5 superpeers - they are fully compaible. I tried it. I think you did not fully understand this- 1.4s will connect to BOTH 1.5 AND 1.3.3. And even if the final move to Morpheus isn't successful - I think a 1.4 network is better than a 1.5+ network, it has less of KaZaA's sneaky features. Please, correct me if you think I still don't understan :) Thanks :) |
wow, interesting theories guys. :) welcome to nu spikologia! :tu: enjoy the boards :beer:
- js. |
All Supernodes communicates with Kazaas servers. In this way Kazaa can remote control all the supernodes and so force the clients to upgrade, lock some older versions out or wake up the altnet from Brilliant Digital. They can probably do more worse things with the PCs of users which are connecteted to Fasttrack.
So Fasttracks servers give the order to supernodes to do something. The reason for the upgrade to version 1.5 is probably only to distinct between desired and undesired clients. |
Quote:
Sounds to me like it's worth trying, as again, there's nothing to lose, and the less control we give KaZaA, the better we can live with ourselves ;) |
Did I miss something?
Ok, so who has a copy of 1.4, I wonder if that site with the store of old P-2-p's has it?
Anyone got the URL for it? Snark:RE: |
Re: Did I miss something?
Quote:
Anyways, in the meanwhile, you can probably hope to find this file on the FastTrack (remember how KaZaA puts its installation file on the shared folder so it can distribute itself? Well you can find all KaZaA's versions since 1.3.3 this way) - the filename is "kmd14_en.exe". just Search on KaZaA or a compatible client (I know this is rather absurd, but there's no better way. Download it, uninstall KaZaA, and install the downloaded older version. I will hopefully have the spyware-free version on the web sometime soon). And if you download KaZaA 1.4 - beware! It seems to include B3D Projector! |
keep in mind all versions of morpheus forward of august 2001 were designed to lock out gifts' opensource project. as such these versions destroyed the network as it then existed. jaan said they could survive in some form but mine finally shut down completely about seven days after the new release. it never connected again in any meaningfull way. in other words, morpheus v1.30 was already vulnerable to sublimation. i can't imagine later versions being any less susceptible.
- js. |
making old morpheus work again
Reviving old morpheus would be cool. I tried to look for a kazaa v1.4 but i only found v1.3.3, 1.3.4 and 1.5. kazaa 1.3.3 doesn't work same as morpheus 1.3.3. However, there is an imorpheus v1.5.1 which seems cool. I wouldn't use grokster/kazaa official versions becuase they send unwanted files to your computer. It would be nice to see old morpheus back up. If you're really serious about making it work again, good luck Spikologia.
|
Hi Spikologia, interesting idea.
I found kmd14_en.exe on FastTrack straightaway - but THREE different versions:
Which version did you test? PS Did you test for BDE etc too? |
Good Luck!
Nice thread, I like the thinking, I'm not sure how successful you'll be, but good luck anyway!
I'll be interested to find out how you get on. Anything that gives Sharman a serious case of indigestion is worth a go, although I think while they are in existence, they will always be in control of the network because some of the Kazaa supernodes are hard-coded into the applications, as well as in the registry. I think as soon as they become aware of the 1.4 issue, they'll find a way to stop it happening. This is why Kazaa Lite is such a good option at the moment, as long as it keeps up to date with the releases; Sharman can't tell the difference between regular KMD and Lite KMD, so they can't be blocked (yet...) |
if my memory is correct, doesnt kazaa do its dirty tricks by automatically changing your registry? if so why not use something like startup monitor to keep it from changing your registry, it warns you (and asks if u choose to allow) ANY changes to your registry.
I run it bc I hate when programs change things i dont want it too. But it could be at least one line of defence against kazaa's out of control behavior. |
This won't work
Startup monitor will only alert you to things that alter the registry that affect your computer at startup. The registry is being updated by programs all the time, not just Kazaa. You wouldn't be able to have something to alert you to ALL of the changes, it's just not feasible!
|
Quote:
|
Quote:
I've checked for BDE - it's there, unfortunately (and Cydoor too, of course. There are also some other apps you can choose NOT to install). Of course this will all be cleaned in the spyware-free version I'm working on. |
@snowman: you can control which supernode a 1.3.3 morpheus accesses at startup. since it cannot connect to musiccity, it uses the supernodes stored in the registry (Connectioninfo).
what you just need is a valid ip of an online 1.3.3 supernode. you can enter this ip as the only ip into the registry. (question is: who runs the supernode and gives us his ip?) the only thing is how to protect this 1.3.3 supernode of being infected by 1.5.1 supernodes. @installation: most of the crap comes while running the installer. the installer is not really needed - what you only need is just the client (i.e morpheus 1.3.3.exe and the registry settings) also for this new clients. (+cd_clint.dll) for new clients we could try to share a reasonable simple zip which contains the grokster1.5.1 exe, some grok.reg and a cd_clint.dll, which just resumes in some simply copy paste installation. only the folders have to be created, the registry imported and the files copied to correct place. |
lets put this issue to rest
I don't think anyone here is confused about what you are talking about. You propose that since 1.4 seems to be 'safe', it can be used to revive the 1.3.3 network; 1.4 also doesn't seem to upgrade older clients, and so can act as a 'bridge' for 1.3.3 clients.
There are at least two potential ways to implement what you propose, all fraught with issues. The most straightforward way is to introduce the 'safe' 1.4 nodes and get them promoted to supernodes withing the bigger network. Then have older clients connect to the 1.4 nodes and hope they'll remain safe. Problem here is that while 1.4 SNs may not get upgraded by new nodes, by joining the network 1.4 SNs will be seeded with many non-1.4 node IPs, which will be cheerfully forwarded to 1.3.3 clients. Since clients connect to multiple supernodes (during one or more sessions), there is a high risk of them contacting a new SN, which will force an upgrade. Reinfection is an issue, but an even bigger risk is, as you said, that for some reason 1.4 is sill allowed on the network. Why? Maybe it's because the 1.4 clients isn't very widespread. Maybe some licencee is still using it. Whatever the reason, even if 1.4 nodes cannot be auto-upgraded, they can easily be disallowed from connecting in the first place. It's only a mtter of time before FT does this; it doesn't buy you any time, and isn't good for shareres. You're just contributing to a dead-end network. Spend your time and bandwidth supporting a better one instead. So the other option is to have a stand-alone network, either because you're locked out, or by choice. If you're locked out and form your own one, there is nothing stopping FT from trying to connect to it and re-infect the older clients within it, should they wish to cause you trouble. Somehow you have to prevent new nodes from connecting to your network if you go this route. But how? Nodes always allow NEWER clients to connect, you can't stop them. Run it on a different port? Sure, but how do you distribute this information (and seed node lists) to enough people to make a worthwhile network? If a small network is what you want, just run an OpenNAP server, it's easier to find and connect to with virtually any existing P2P client. The sticking point is that, yes, technically the FT network can run split up by version numbers, assuming it is left alone. Which hasn't been the case. As soon as an 'outdated' node touches a higher version supernode, it will be upgraded and moved to the new network. If there was no automatic upgrading (which you don't know for a fact is the case with 1.4), then same version clients would stick together. BUT, FT/Kazaa is bent on moving everyone to the new network, for obvious reasons, and any attempt at a separate network of any significance will be disbanded by auto upgrades. And if your idea IS to run a small network, there are better ways to do it, and we already have an OpenNAP server for NU you can connect to. |
Reviving old Morpheus
I downloaded the kazaa 1.4 version from fastrack. It told me about an upgrade and I said no and it connected. I belive that if people would just use this version, the old morpheus will work again. People we would have to convince people to use this program. BTW, does anyone know if kazaa v 1.3.3 still works? Will will download it too to give it a shot. For all you people how know how to do web sites, put the file on your web site and tell people about it so they can download it. Remember, the original refo search? Why not do what was done with that program. If you were to do this, you would have to find some way to block out the pc's ip address so you can't be traced.
|
Kazaa Download site
Here is a link to download kazaa media desktop v1.4. <a href="http://www.geocities.com/junistar69">Kazaa</a> or http://www.geocities.com/junistar69/Kazaa.zip
|
Re: Reviving old Morpheus
Quote:
Notice an upgrade WAS suggested to the v1.4 node, but wasn't required. As long as the "notify before installing automatic updates" option is selected (and it is selected by default) at the Options > User dialog, the user should have a choice not to update, i think. Thanks for your support, thegame412, but the v1.4 idea isn't yet ready for wide distribution. We'd better think together of all the possibilities, and decide for the best way to follow this plan, if at all. Also we shouldn't distribute the official KaZaA v1.4 - it has Cydoor and BDE, we don't want that. My spyware-free version will be ready when we decide what to do. Thanks again! |
Plan update
Thanks for all your replies and support, guys.
I have decided to rethink my idea, in order to achive a more complete plan. I will also try to show how I think this could work, considering all your replies. This is just a thought, please tell me what you think. Also - what do you thikn, is this idea good enough for me to start posting links to this thread on other forums, so more people could give their thoughts of it? So here it is. Our main goal should be taking FastTrack back to the times when most of its dirty tricks weren't implemented yet. This inculdes BDE and it's automatic reinstallation by KaZaA (there are rumors that KaZaA Lite tries to reinstall BDE too, though this is not confirmed. Anyways, in the next version of KaZaA, it could be pretty simple for Sharman to make sure that hacked versions like KaZaA Lite would reinstall BDE too), and the dirty ways to get rid of older, cleaner clients. We do it step-by-step - first we'll distribute a hacked version of KaZaA v1.4 without spyware (I'm starting working on this now) and promote it. The promotion should also make sure that people understand that to make this efficient, they should do their best to keep their computer on (together with the hacked v1.4 online) for as much time as possible, favorably all the time, so that even if FastTrack tries to take them down, they won't ave a chance to catch them upon login, as they're already logged (a few machines disconnecting from time to time is ok, as long as there are enough v1.4 supernodes still available). Also the promotion should advise people who insist on using v1.5, v1.5.1 or v1.6 not to download any future version newer than v1.6 (like v1.6.1 or v1.7) as they might include a mechanism to drop v1.4 off the network, just like they dropped v1.3.3s. In case KaZaA DOES manage to drop some of the clients, using their "auto upgrade" strategy (if we promote the idea well, they shouldn't be able to this as efficiently as they did with Morpheus, and hopefully we would still have a considrable amount of v1.4s still connected to the wide FastTrack network), we quickly alert users on a dedicated websites to send in their ConnectionInfo if they have a v1.4 still running, so we can produce a fast regfix with an updated list of working supernodes. This time we will be ready for KaZaA's "attack" and will be ready to handle it. Sure, we can't be sure it would work, but I think it's worth to try. More older clients on the network means a BETTER experience for us, the users, and much less power in KaZaA's hands. The next step is optional. We'll do it if everything goes well and KaZaA fails to remove v1.4s from the network. However, if KaZaA does have some sort of success in reomving them, we'll reconsider this step. When we beleive there are enough v1.4s on FastTrack (hopefully we could use polls on major p2p sites to find that out), we can launch a Morpheus v1.3.3 promotion. Since v1.4 connects perfectly to the wide FastTrack network as I've shown before, and probably doens't block v1.3.3 clients (this isn't proven, but likely, since v1.3.3 wasn't blocked when v1.4 came out, and probably wasn't planned to be as v1.4 was only available on KaZaA and not on Morpheus or Grokster), we can use it as a gateway between older Morpheus v1.3.3 clients and the wide FastTrack network used by current versions of KaZaA, Grokster, and iMesh. This will not only make Morpheus clients usable again, it should also let them connect to the whole FastTrack network, and not just an independent one of old clients (which can be easily infected and taken down because of the small number of users). And why would we want people to use 1.3.3? Because it surely has less of KaZaA's tricks, and could possibly allow users to feel more safe with their p2p expereince, especially if they can use the official, not-cracked, Morpheus 1.3.3, which has no spyware to start with, as we all know. As I said this step isn't required, and we might be satisfied enough if the FastTRack network is full of v1.4 clients which KaZaA has less control of. BTW, I've been thinking on a name for the project, website, and hacked v1.4 client :) This isn't very important at this point, but how about "reConnect", or maybe "reKonnect" (the K for KaZaA, of course). Please post your thoughts! |
What's the point?
You've obviously spent alot of time thinking about this, but to be honest, what's the point?
You're never going to convert the "ignorant million" who have blindly downloaded Kazaa without even thinking about what else they've signed up to, or who is in control of their machines. Most of them are kids who don't know any better. I just don't think it's worth the effort. While we can still use Kazaa Lite, or any other spyware-free versions of Grokster or IMesh, you might as well carry on doing this. So long as you stay vigilant about what's happening to your system you'll be OK. There was nothing particularly special about Morpheus 1.3.3, I wasn't even particularly fond of the graphics to be honest. Ride the wave and enjoy it, don't struggle against the tide for no reason. |
Re: What's the point?
Quote:
I agree I might have not made my point very clear, I hope I do it right this time: Sharman Networks are for sure pissed of the situation caused by KaZaA Lite - naturally they can make no money this way. I'm 100% sure that if Cydoor wants to continue its existence, they're working right now as we speak to get a newer version of Cydoor which will make it much harder or even virtually impossible to produce Dummy Cydoor DLLs like the one KaZaA Lite is based upon. KaZaA will then release a new version which works with the new Cydoor, and eliminate all older releases by requring them to upgrade. Since a Dummy DLL can't be created for that new Cydoor, a new KaZaA Lite version can't be created, and all KaZaA Lite versions would be eliminated. Or, Sharman could do a worse thing - they could drop the Cydoor model completely and partner with BDE to replace KaZaA with a subscibtion-based service, and of course eliminate all older versions including KaZaA Lite. The only way to make sure FastTrack don't do what they did in the past with Morpheus, only this times without giving us any alternatives, is to act BEFORE they do. We can only feel safe and stop worrying about this when we have a real alternative (hopefully giFT\OpenFT would be a very fine alternative once released). |
Is this good or bad
I remembered a few days ago trying kazaa 1.3.3. Today I decided to try grokster 1..3. and though it did say a newer version was available , it still connected to the fastrack network. BTW, I'/m on grokster 1.3.3 right now. What does this mean in terms of trying to revive old morpheus 1.3.3. Is this good news or bad news.
|
Re: Is this good or bad
Quote:
Anyways, it seems to me that people aren't interested in tis finding. Then again, as KaZaA now tries to get rid of KaZaA Lite, this might be useful. We'll see. |
Well I found Grokster 1.3.3 somewhere and it doesn't work - you might have gotten into an independent "iMorpheus"-like v1.3.3 network which collapsed soon after. This cannot be used to revive anything :)
Anyways I agree with some of the posts here - there is no real use and bringing Morpheus 1.3.3 back, although I truly beleive this is possible with KaZaA 1.4. However, KaZaA Lite isn't our solution. Sharman Networks already declared war on KaZaA Lite, and working together with Cydoor they could probably easily eliminate KaZaA Lite (by making sure next versions of KaZaA can't be hacked, and then dropping all older versions). KaZaA 1.4 might help with this, as it seems it wasn't eliminated from the network, while KaZaA 1.3.4, a NEWER release (even though the version number is smaller, 1.3.4 is newer than 1.4) IS blocked from the network. The big question is - why isn't KaZaA 1.4 isn't blocked - is it because it is still used by some lisencee (like iMesh maybe), maybe because they just forgot it existed, maybe they didn't think it's enough widespread to block, or maybe some difficuly arised when they tried to block it. If the latter is correct, KaZaA 1.4 is the answer to all our FastTrack-related problems. If not, it can still be used to make sure we have a spyware-free alternative, but newer versions MIGHT be better for this. |
Grokser 1.3.3
Spikologia, did you just get the message with grokster 1.3.3 that it was to old to connect to the network or did it just ask you to upgrade. If it just asked you to upgrade, just click no and it will eventually connect. If it did tell you that it was too old to connect to the network, then maye it will be blocked out soon. Right now, i'm use grokster 1.3.3 and there are currently 1435903 users online sharing 259715k. Also, my username is someone@??? not someone#grokster. I'm pretty sure that this is because I'm using version 1.3.3. I really liked it when morpheus was around. The downloads were much faster. Now there are slow. Even people with broadband say there downloads are slow too.
|
Spikologia I just wanted to say that I am very interested in your findings and also in this project. If there is any assistence which you need or require please ask me on my forums located here
http://www.kazaa.mirrorz.com I run the new forums for the Kazalite program and would be glad to help you with anything that I can. Regards, Harbynger (one of many names I use) btw TankGirl you are also invited to drop by for a visit and yes of course the rest of you are welcome as well. : ) |
welcome to nu Harbynger, stop in again:beer:
- js. |
Hi Harbynger and welcome aboard! :beer: You have a nice site with a lot of informed discussion going on, congratulations for the good work! It is always encouraging to see p2p users organizing themselves into these well-informed subcommunities that have a life and continuity of their own whatever the venture capital guys decide to do with their commercial applications. :tu:
This has been a great thread and I have followed the smart contributions of Spikologia ( :W: ) and others with great interest. KazaaLite in itself is a wonderful countermove against Kazaa's disgusting spyware policy. I feel no sympathy for Kazaa/Sharman and would love to see the entire network taken out of their hands under community control. :sup: :uzi: However, as colinmacc pointed out, the prospects and potential gains of such a project are questionable. At best one could hope to form a spyware-resistant subnet inside a larger network that Kazaa controls and profits from. Doing this with a hacked client whose inner workings are not thoroughly known is not an attractive idea. To make the client even reasonably safe and robust all automatic software upgrade functions plus all hardwired connectivity to Kazaa-controlled servers should be neutered from it. This would still just provide the protection for the subnet itself; it would remain in the hands of Kazaa whether to allow the client to connect to the main network under its rule. Assuming that the above safety problems could be handled and that Kazaa would not quickly kick the client out (which is a lot to assume) we would still be left with a modest client with no bug fixes, no development, no future. And that is a real bummer. The p2p engine has been the only good part in the FastTrack clients (providing good file transfer and connectivity mechanisms) but otherwise the clients have been bloated, buggy and resource-hungry, in other words typical beta software under development. The client would dearly need better bandwidth/queue controls, a decent chat window and working hotlists, not to mention the obvious scalability issues (limited search visibility). In the present situation I would not hold my breath to see any client development done by Kazaa (besides bundling even more spyware that is) - and with a hacked client there would be no hope of development at all. ;( Much the same has happened with FastTrack that happened with Napster: when the network become #1 brand and the center of gravity for file sharing the client development was effectively stopped and whatever communication there had been between the companies and the users came to a halt. The focus is on money, control, legal issues etc. - not the best of environments to do long-term software devopment and to work on customer satisfaction. - tg ;) |
Hello, Jack Spratts and TG (Tankgirl) I appreciate the warm welcome from both of you I must admit your board is excellent and does indeed FAR EXCEED mine. lol, (i)putting my jealousy(/i) aside (that your board looks better than mine) ;)
I wanted to say that I feel very fortunate to have found your site especially the peer2peer forums...everybody has their favourite area so I guess this would be mine. It's very nice to see thoughtful and intelligent people posting as you both do and so many others who visit and join these boards. A little about me: I was introduced to the world of filesharing (post Naptster) It was through KaZaA that I first learned what it is and what it was capable of . Filesharing is not crime in my way of thinking it is merely a tool much like an automobile ...right now for me Fasttrack is simply a major highway and Grokster/KaZaLite/KaZaA are simply different "models" for the vehicle that i use to get to my destination (what i want e.g., "files" whatever those files maybe "shareware" freeware, etc.) It took me a while to fully grasp the concept of sharing and after I caught onto it I loved the concept and I loved the ease of use and simplicity of the original KaZaA (1.32) However (i say Greed...because really if it was you or me who invented either Napster of KaZaA wouldn't we want to make money off of our idea too? I know that I would and I hope that doesn't make me a bad person) Nevertheless it was the original PhP based KaZaA messageboards that really cemented me on the concept of filesharing clients...The messageboard felt like a "community" and it for a long time it was like home to me...one that I dearly missed when it was taken away...hence KaZaLite forums were born! Me and a friend of mine who goes by the name "Mitnick" founded these forums and co-moderate them. I don't want to be too wordy at this time other than to say I'm glad I found your site and I do hope some of you will visit as I will keep an eye open here as well for new and exciting discussions.. My favourites of course will be those centered around KaZaA and how to make it better. Your suggestions Tank Girl were very good I shall consider them...i hate to give away too much because it will be quite some time before my client is ready for a betatest but I'm working on yes yet another FastTrack based program similiar to KaZaLite but which will contain my own unique style/twist and flavor with it so to speak. I could probaly use people whom are familiar with networking and packet structure, API programming, visual basic, some cracking/hacking knowledge would be good. My old vision for this client was to have it contain all the codecs necessary to view movies like SMR patch, Intel codecs, Angelpotion, DivX5 and one other codinstal.exe (can't remember the more familiar name) I was gonna keep the same interface as the current KaZaA client only getting rid of the bde and if i can removing the or unintegrating the cydoor so that even a hacked dll would not be necessary...in light of this discussion there appears to be much more work needed...i also wanted to do away with the windows media player being incoporated into the program (that needs to go it rarely functions anway) I apologise for my long speech...usually if its long it doesn't get read and who is to say if its worth reading anyway. Take care all. Until, the next time -Harbynger : ) |
Thanks for all your comments, guys.
Thinking on things pointed out by TankGirl and colinmacc I have decided to do some more research, instead of jumping into this project which indeed isn't enough formed at all. thegame412's comment of Grokster 1.3.3 being able to connect to FastTrack made me realize something - although I couldn't get Grokster 1.3.3 to connect on my computer, it might be able to. Upon first launch, Grokster 1.3.3 tries to connect to the network. It then offers to upgrade to 1.5.1 (Morpheus didn't really offer an upgrade, it just told the users to upgrade without giving any upgrade to download). If you choose "Yes", "GroksterUpdate151.exe" is added to the Download list on the Traffic window. On my pc, Grokster can't connect, and only shows "5 users online". However, in order for an upgrade to happen, Grokster MUST connect, and thegame412 claims it really did, on his computer. thegame412 - could you please post your Grokster registry settings so I can check 'em out? To do that, go to Start menu, and click "Run...". Type "regedit" (without the qoutes) and hit ENTER. Open the HKEY_LOCAL_MACHINE\SOFTWARE\Grokster "folder" (it's called a "key", actually, but has an icon of a folder) and make sure that you've clicked the Grokster "folder"\"key". Then choose File > Export, choose a name for the file, save it, and post it here. Thanks! Please tell me if you're having any troubles with that. Also, I've found that KaZaA 1.3.4, released soon after (yes, after) KaZaA 1.4 does connect to FastTrack, although I previously thought it didn't. I don't think that this is because something changed, I probably just did my tests wrong last time. I'll do some more research and see if this can help us. And Harbynger - thanks for you invitation. I'll drop by soon :) |
you may try a recent list of supernodes for grokster
import the the reg file. you may first have a look at it with a texteditor - it only conatins the "connectioninfo" |
Hi guys/grrlz I just had an idea...it may just have been a brain fart I will leave it to my very nimble and adept associates to decide whether or not it indeed is an idea or not.
First off some background please look at this link by Indiana on another board http://pub45.ezboard.com/fmorpheusfr...picID=30.topic And then there was one more idea...but I seem to have now forgotten what it was :\ sad i know so the rest of this will basically be my "rant" so to speak. Okay here is the deal with me. I am not a programmer but I have what I would say is a "keen" mind (your opinion of this may vary) and I have found that sometimes in my life there are problems or complexities that totally beleaguer me and my puny wit just cannot fully grasp the concept of something then at a certain time however sometimes much later I soon achieve Nerdvana in that I can now understand or grasp a formerly unfamiliar concept. :) with that said I must make mention that currently I am not a programmer but due to my interest in this puzzle piece that I call KaZaa I am doing my best to learn as I go and probe deeper into the mysteries of this "proof of concept" application. Speaking plainly my love of a mystery prompts me to investigate it and therefore I want to learn what makes this program tick. Indiana Jones has offered some good clues in the form of the registry entries and values and I myself have seen this "magic" four digit number changed when connecting to a certain ip address which I have recorded elsewhere. It is one of the servers ran and owned at least it was registered Niklas Zennstrom when I did a whois inquiry....now get this I tried Indie's reg trick on an old morpheus 1.33 client that didn't have the bde installer wrapped around it...and Using my dial-up connection ( i think it's important to note my connection type as somehow the fasttrack clients are able to determine your bandwidth in the regulation of who becomes and ultrapeer/supernode) and my Ulitimate firewall (or at least it used to be Windows Nt breaks the logging function in it) Atguard 3.22 I was able to keep a list of all the connections and attempted connects by the morpheus 1.33 client (using the reghack posted on VLaibb's site (ran by Indy I believe) and I was able to record the exact Ip address that cause the message "Your client is too old to connect and needs to upgrade" I will post this ip if you are interested but I do not support the idea of DDos'ing this ip address as that would be wrong and there are better ways to get around this by working with the program code to find the upgrade mechanism's on/off switch and either yank it out or permanently turn it to the off position. I'm trying not to post to much in one posting....forgive me and bear with me please. Basically the point of this post is that There is a supernode controlled by KaZaA that gives the notice. Also this is done in realtime meaning I was viewing the key in regedit at the time of the connection to the ipaddress that caused the value in the registry to modified... Now my question to the board is this: Are there any freeware or shareware applications that can Protect your registry or lock it from real time modifications (not accesses such as read functions but write functions only?) I hope this information is useful. -Harbynger |
Grokster registry
I am unable to currently export the grokster registry becaue I'm not home. I will do it once I get home.
|
indiana jones - Thanks for you reg file, but it didn't work... Guess something is still missing...
thegame412 - ok, thanks. And please tell me if you're having any troubles. It is very interesting if Grokster 1.3.3 can still connect to FastTrack! |
|
Here's Grokster reg key
http://www.geocities.com/junistar69/Groksterregkey.zip Spikologia, If you don't get the message saying that your version of grokster is too old to connect to the network. Please download updated version from www.grokster.com, then it should eventually connect. I too first had just five user online when connected on several occasions. I gave it a few minutes and then it read 1 millon users online. So if you say that it says 5 users online, just give it time and the number will increase.
|
All I want for Christmas...
...is a FastTrack network built by the Users and for the Users.
I think it's great that there's alot of other people who feel the same way. I guess this was the sort of thinking that spawned the GiFT project. Anyway, keep up the positive thought, this has been a most interesting and enjoyable thread, and anything that attempts to thwart the evil schemes of Sharman/Kazaa/Brilliant Digital is worth trying for. |
Hi all I found this link to the Developer's forum for KaZaA lite on another fan site for the program. Here is the link:
http://kazaalite.lunarpages.com/cgi-...DaysPrune=1000 If i have to jump up and down like that guy (the Vp of Microsoft) to get the attention of you developers out there...i will (jumps around like a monkey flailing arms wildy while screaming:) DEVELOPERS, DEVELOPERS, DEVELOPERS! This is what we need... On a side note I've been in contact with one of the programmer's for the original KaZaA and he said I should talk to either Janus or Niklas about the KaZaA Media Libs but Niklas and Janus are not interested in giving away the source code they did tell me they would sell it to me and were very pleasant until they found out I had no money or at least not the kind of money they were talking about : ) After that all communications with them ceased...kind of like my landlady for Five years she was so nice...then you get laid off can't pay your bills and all that changes... Well enough about me...things are better now (that was a while back...but its a story for another time some place else) Peace and Love all. Keep on cracking : ) |
why bother, morpheus has gone the way of napster, so well. it was good while it lasted. but so was scour back in the day.
kazza works fine. next it will be something else. and the beat goes on... |
originally Greedy I was not going to answer your question...then in poking around my old cd collection I found this exact same subject being discussed on the Morpheus forums (some of which I have archived) and decided it would now be appropriate to answer you with a quote by Indiana Jones from the old Morpheus forums as it pretty much sums up my feelings as well (for the most part)
Without furthur adue: Quote:
:) |
I hope this doesn't make too big of a mess but here is that whole post in its entirety that I had saved to a cd someplace...
hope this is helpful to the discussion: Because this is a free service pop up ads will appear. I suggest using a popup killer. Morpheus > Questions > registry edit for morpheus 1.3.3 reconnect Next Topic >> Author Comment IndianaJonesAIBB Registered User Posts: 34 (2/27/02 8:22:30 pm) Reply registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- hi i found a registry edit which worked for my much to old 1.3.3 i replaced a 0d (red) [b] [HKEY_LOCAL_MACHINE\Software\Morpheus] "FirewallStatus"=dword:55555555 "network_config"=hex:00,00,00,0D,00,00,00,00,3a,4b,61,5a,61, 41,00,43,6f ..... by a 05 (yellow) [HKEY_LOCAL_MACHINE\Software\Morpheus] "FirewallStatus"=dword:55555555 "network_config"=hex:00,00,00,05,00,00,00,00,3a,4b,61,5a,61, 41,00,43,6f ..... and it stopped saying its to old and connected after a while afterwards it replaced the 05 by 18 but it reconnects after restart indy ----------------------- File: surprise.mp3 Length:5845871Bytes UUHash:=1LDYkHDl65OprVz37xN1VSo9b00= Copy the lines above and use the 'Paste from Clipboard' function of sig2dat 3.0.a to create a startfile for your FastTrack p2p client for safe download! djakrse Registered User Posts: 24 (2/27/02 9:45:11 pm) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- good deal, Indy.. i had 13 where you had 0d, but puting 05 in its place stopped morpheus from throwing up the message box telling me to update morpheus. no idea what the dif is, but who am i to argue. btw, kazaa has 11 in that 4th slot.. all the other numbers are the same. ...and i just noticed that kazaa 1.5 has an entry for CloudLoad in the registry. I imagine this new cloudload must be the "technology" which morpheus was incompatible with. and i assume grokster 1.5 must have this feature too since it isnt supposed to have problems right now. djakrse Registered User Posts: 25 (2/27/02 10:19:14 pm) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- questions for those who know or can find out about these settings: Quote: -------------------------------------------------------------------------------- "IndianaJonesAIBB said: afterwards it replaced the 05 by 18" -------------------------------------------------------------------------------- when kazaa and morpheus connected as i was checking the options, it changed the aforementioned 4th number to 18 (from 11 for me) -- Does this mean that this number is determined by the fasttrack login server when you connect? im aware these clients supposedly dont have to login to connect to the network.. it happens when you get username@???.. but does that have something to do with why the network wasnt working for morpheus? comparing kazaa 1.5 and morpheus 1.3.3: i found that one setting in registry (Win9x only).. [HKEY_CURRENT_USER\Software\Morpheus\UserDetails] "PromptBeforeInstalling"=dword:00000001 .. which implies 2 dif things in User tab Options: "Notify me when new updates are available" - Morpheus "Notify before installing automatic updates" - KaZaA ..hmmm. also while comparing kazaa with morpheus in the registry.. [HKEY_CURRENT_USER\Software\Kazaa\Settings] "UseCount"=dword:00000000 "Date"="02-15-2002" "WarnShare"=dword:00000001 where as morpheus only has: [HKEY_CURRENT_USER\Software\Morpheus\Settings] "WarnShare"=dword:00000001 1) what's up with "WarnShare" could that be an upcoming feature? 2) "UseCount" sounds like a way to tell how many times you have used morpheus/kazaa or dloaded a file.. times $$ per file = monthly bill? 3) "Date" ..what is that? related to future features mebbe. not sure im liking the looks of that IndianaJonesAIBB Registered User Posts: 35 (2/27/02 10:32:33 pm) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- last time i heard a bout cloudload befor meopheus forum wennt down. it was a business plan to sell users disk space an bandwidth to companies which offer huge data for download but suffer from high bandwidth cost. they should then only have to offer some p2p client and the download in fact should take place from a 'cloud' p2p users. the data should be "forced" placed on all high powered high bandwidth computers. there was a short discussion then the board was killed. i dont know more about the regs here. just the Connectioninfo contains IPs of supernodes , the client troes to connect to if it cannot connect to music city supersupernode indy ----------------------- File: surprise.mp3 Length:5845871Bytes UUHash:=1LDYkHDl65OprVz37xN1VSo9b00= Copy the lines above and use the 'Paste from Clipboard' function of sig2dat 3.0.a to create a startfile for your FastTrack p2p client for safe download! BuzzB2K Registered User Posts: 31 (2/27/02 11:27:52 pm) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- Hey guys I am sure you have noticed some users who say either they don't get the "too old" message or have no trouble connecting. My Morpheus never gave me the "too old" message, and after I looked in the registry I found that there was allready an 18 in the fourth position... So it looks like you are on to something there... Buzz I used to think I was indecisive, but now I'm not sure IndianaJonesAIBB Registered User Posts: 36 (2/28/02 12:57:37 am) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- hey buzz - since you run grokster 1.5 too - could you try to use grokster 1.5 network_config for morph or post it here? ----------------------- File: surprise.mp3 Length:5845871Bytes UUHash:=1LDYkHDl65OprVz37xN1VSo9b00= Copy the lines above and use the 'Paste from Clipboard' function of sig2dat 3.0.a to create a startfile for your FastTrack p2p client for safe download! BuzzB2K Registered User Posts: 32 (2/28/02 7:23:59 am) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Grokster] "network_config"=hex:00,00,00,19,00,00,00,00,3a,4b,61,5a,61, 41,00,43,6f,6e,6e,\ 65,63,74,65,64,4e,65,74,77,6f,72,6b,73,3a,47,72,6f,6b,73,74, 65,72,20,66,69,\ 6c,65,73,68,61,72,65,20,4d,75,73,69,63,43,69,74,79,00,00,00, 00,00,3a,47,72,\ 6f,6b,73,74,65,72,00,43,6f,6e,6e,65,63,74,65,64,4e,65,74,77, 6f,72,6b,73,3a,\ 4b,61,5a,61,41,20,66,69,6c,65,73,68,61,72,65,20,4d,75,73,69, 63,43,69,74,79,\ 00,00,00,00,00,3a,66,69,6c,65,73,68,61,72,65,00,43,6f,6e,6e, 65,63,74,65,64,\ 4e,65,74,77,6f,72,6b,73,3a,4b,61,5a,61,41,20,47,72,6f,6b,73, 74,65,72,20,4d,\ 75,73,69,63,43,69,74,79,00,00,00,00,00,3a,4d,75,73,69,63,43, 69,74,79,00,43,\ 6f,6e,6e,65,63,74,65,64,4e,65,74,77,6f,72,6b,73,3a,4b,61,5a, 61,41,20,66,69,\ 6c,65,73,68,61,72,65,20,47,72,6f,6b,73,74,65,72,00,00,00,00, 00,dd,00,52,65,\ 71,75,69,72,65,64,43,6c,69,65,6e,74,45,6e,63,72,79,70,74,69, 6f,6e,42,69,74,\ 73,3a,34,31,00,52,65,71,75,69,72,65,64,53,75,70,65,72,6e,6f, 64,65,45,6e,63,\ 72,79,70,74,69,6f,6e,42,69,74,73,3a,34,31,00,43,6f,6e,6e,65, 63,74,50,72,6f,\ 74,6f,63,6f,6c,48,65,61,64,65,72,56,65,72,73,69,6f,6e,3a,33, 00,41,75,74,68,\ 55,72,6c,4d,61,73,6b,3a,35,00,42,72,6f,61,64,63,61,73,74,53, 74,61,74,73,43,\ 6f,6e,74,72,6f,6c,4e,6f,64,65,73,3a,31,35,32,2e,37,2e,32,34, 2e,31,30,31,3a,\ 31,32,31,34,20,32,31,32,2e,31,37,39,2e,33,35,2e,31,31,38,3a, 31,32,31,34,20,\ 31,32,38,2e,31,36,33,2e,36,31,2e,32,30,33,3a,31,32,31,34,20, 32,34,2e,35,31,\ 2e,38,32,2e,31,31,33,3a,31,32,31,34,00,2f,98,24,ae,c5,46,72, 7f,48,75,25,d4,\ b0,14,61,3f,6f,4c,ef,41,df,10,9f,50,78,02,20,02,57,46,1c,e7, aa,20,df,ed,33,\ f8,fb,21,d6,dc,4c,e0,cd,94,6d,de,28,c7,d4,c9,de,45,04,67,49, 02,05,de,17,bd,\ 08,ba,23,52,9a,a1,ee,fe,0f,20,a4,06,29,3e,fc,e7,59,11,07,fd, e8,23,a3,5b,32,\ 58,37,d7,2f,ef,80,aa,ec,fc,47,21,11,89,b5,b0,aa,84,5e,2f,36, c7,a0,f8,a9,72,\ 24,0e,be,a5,84,d7,d0,13,5f,8a,6c,3f,d9,f2,26,49,2e,c0,f8,7f, ef,ee,0a,0d,40,\ b1,b7,00,9d,db,67,95,ba,df,12,8d,50,54,98,02,66,4a,5d,84,07, 43,ce,76,17,9c,\ 9f,6e,3d,3a,52,f1,6e,d6,4f,c6,19,98,0d,68,89,b3,9b,9b,20,7f, ba,2b,ee,3b,9f,\ c4,e0,a5,b6,a9,de,d3,20,8e,c7,f5,46,9d,7c,e8,99,b7,32,46,db, 89,8a,df,f9,24,\ 39,c5,26,9d,21,15,23,31,b4,f3,2e,ac,8d,f8,f4,d7,62,5d,af,02, e1,2f,b8,15,bc,\ 52,92,bb,fe,b3,c9,37,3f,a7,1f,c7,3b,1d,c8,cc,37,8e,e1,8e,3c, 4b,61,5a,61,41,\ 53,69,67,6e,61,74,75,72,65,3e :smokin Buzz I used to think I was indecisive, but now I'm not sure teambilly Registered User Posts: 3 (3/4/02 4:21:50 am) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- hey, i tried this reg edit, and it works, but i am only showing 98 users online, and after a few disconnect/reconnect it doesnt seem to get much higher.. 3/6/02 - better now, i've got 30,000 users online now.. getting better search results and downloads... Edited by: teambilly at: 3/6/02 6:32:21 pm BuzzB2K Registered User Posts: 52 (3/4/02 7:01:25 am) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- You need to give up on the old Morpheus and install Grokster like most of us are doing... Quote: -------------------------------------------------------------------------------- Grokster without Spyware (With Pictures!!) posted by wiggum on March 03, 2002 @ 07:32am With Morpheus no longer connecting to Fasttrack many people having been thinking about converting to another fasttrack client. Grokster connects to Fasttrack but has spyware installed with it. Running Ad-ware in the usual way after installing Grokster will not let most people run Grokster. Project Insomnia have published a way of getting around this: follow their steps here to run Grokster without Cydoor Spyware. Installing Grokster without spyware -------------------------------------------------------------------------------- Buzz I used to think I was indecisive, but now I'm not sure Edited by: BuzzB2K at: 3/4/02 7:03:28 am IndianaJonesAIBB Registered User Posts: 38 (3/6/02 7:53:13 pm) Reply Re: registry edit for morpheus 1.3.3 reconnect -------------------------------------------------------------------------------- 3/6/02 30000 sharing 17TB its interesting that @fileshare users seemlingly can connect to both nets. morpheus and grokster are completely separated through the different registry entries - that morph has to be deinstalled to run grokster is simply a lie from grokster to eliminate morpheus. i have the exe's in the same folder and they use the same shared folder - they just cannot run at the same time. i just think its fine that the net can be kept up without control to MC's central servers. - its just how the linux kazaa works, you need the ips of a 1.3.3 supernode and you get further ips. i think linus people could connect to this independent 1.3.3 net with their old kazaa clients. is there any linux forum out there? i in no way hang onto the MC people - but since mopheus 1.3.3 cannot connect to a master server makes it really friendly for me. something other - i saw people connecting from different ports than 1214 - is there a hack for that? indy ----------------------- File: surprise.mp3 Length:5845871Bytes UUHash:=1LDYkHDl65OprVz37xN1VSo9b00= Copy the lines above and use the 'Paste from Clipboard' function of sig2dat 3.2.a to create a startfile for your FastTrack p2p client for safe download! twinspan Registered User Posts: 1 (3/6/02 8:29:00 pm) Reply what's the point? -------------------------------------------------------------------------------- dum noob question here, but if KaZaa and Grokster still connect to the FT network, what's the benefit in hacking to old Morpheus version? I'm not saying there is none, I just want to know what it is before I start trying to delve into my registry. IndianaJonesAIBB Registered User Posts: 39 (3/6/02 9:03:33 pm) Reply Re: what's the point? -------------------------------------------------------------------------------- i just find the idea fascinating, that there could be e second FT net, which couldn't be forced to be updated or shut down by any master server(s) - like it happened just recently - simply because it doesn't connect anymore to this Master server(s) what i watched: a startup i.e. morpheus tries to connect to MC server to logon - if it were successful it got a list of supernodes and started to connect - if not (like now) - it startes to connect to a supernode, stored in the registry (Connectioninfo). therefore you just need supernodes which are connected to each other and a list of them for each user and you can keep up your Master independent FT net, which is surely not so easy to control or to monitor like the one, which always is somehow connected to a Master. its just an idea to play with it. indy ----------------------- File: surprise.mp3 Length:5845871Bytes UUHash:=1LDYkHDl65OprVz37xN1VSo9b00= Copy the lines above and use the 'Paste from Clipboard' function of sig2dat 3.2.a to create a startfile for your FastTrack p2p client for safe download! twinspan Registered User Posts: 3 (3/6/02 9:22:09 pm) Reply independence day -------------------------------------------------------------------------------- so this way, we can stay free of Sharman's clutches? When I finally gave up on old Morf, I uninstalled it and tried installing Grok. But that failed, so now I'm running Kazaa. What's the expert opinion: Shd I hack Kazaa, re-try & hack Grok, or re-install Morf/Refo (both of which I got on CD-R somewhere)? (keeping in mind I'm a newbie) Thanks. thegame412 Unregistered User (3/12/02 9:44:33 am) Reply Question about Morpheus -------------------------------------------------------------------------------- I'm currently connected to Morpheus as thegame412@???. That's what it says. How come it doesn't say musiccity. It doesn't bother me. I'm just corious. And about the registry. Mine has a 36 in the fourth slot. When I changed it back to a 5 from 24, it went to a 26. Kamorph Unregistered User (3/18/02 2:56:57 pm) Reply This is interesting @#%$ -------------------------------------------------------------------------------- Looks like we can keep up a separate FastTracknetwork all by ourselves. Streamcast, Sharman, RIAA and all those other would be moneymakers can't stop us. Wow man this is gonna have some impact!! JohnDoe345 Registered User Posts: 167 (3/18/02 10:46:48 pm) Reply Re: This is interesting @#%$ -------------------------------------------------------------------------------- Quote: -------------------------------------------------------------------------------- Looks like we can keep up a separate FastTracknetwork all by ourselves. -------------------------------------------------------------------------------- This was suppose to be the promise of the uncentralized network. If the company goes down then the p2p program is suppose to survive on its own. Although, in this case it has taken a different turn. Users want to use the older Morpheus but not the new one. I think that this would've caught on more if Grokster (without spyware) wasn't a good alternative. Although, it is something to keep in mind for the future in case more p2p companies start selling out to the RIAA, etc. Next Topic >> Email This To a Friend Topic Commands (Moderator only) Subscribe Click to receive email notification of replies Unsubscribe Click to stop receiving email notification of replies jump to: QuestionsMusicMoviesSoftware/HardwareFakesGeneralChangesLogo - Morpheus - Questions - Morpheus Info - About MP3s Powered By ezboard® Ver. 6.6.4 Copyright ©1999-2002 ezboard, Inc. |
1 Attachment(s)
most people probably aren't interested in this anymore unfortunately for me this still holds a great deal of fascination.
i found this link to a german webpage here is the translated version (translated poorly into english by the google interpreter engine) http://translate.google.com/translat...F8%26oe%3DUTF8 Basically what it says is that if you find a working supernode just register its ip address in place of the supernode.kazaa.com and supernode2.kazaa.com in your hosts file that way you will be able to connect with an older client to the network...(this was done for the Linux version) also if you are a windows user...here is a reg file that works as of Friday, May 17, 2002 Enjoy Click the link to download the reg file (for 1.4 user's only) |
| All times are GMT -6. The time now is 12:21 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
© www.p2p-zone.com - Napsterites - 2000 - 2024 (Contact grm1@iinet.net.au for all admin enquiries)