Take a look at Justin's.plan from March 10th. (Thank you google cache) He was working on WASTE then. I think it is safe to say that this was not a hack, and I believe that Justin has the authority for such a release. Gnutella was retractable because the license agreement it was released under allowed for that.
WASTE was released under GPL, and as far as I can tell, it has no such provisions. In fact, it seems to be the contrary. If you accept the agreement, you are given the right to redistribute as long as the GPL is included.
Well, whenever it came online... I KNOW I was a freshman or a sophomore, so that would be late '94 to '96 when I first found it. I've still got a user ID that is 8000 or so. So quite some time ago.
I feel strange writting this, but I can't help but feel the same about the internet as a whole, and even great sites like/. I used to live on this website back in '94/'95 or so, when I first discovered it, and now I just read it every now and then.
Back when my best source of links was Justin's Links from the Underground, and Yahoo hadn't even come on-line yet, I felt as though I'd visited half of the websites out there. Now I only have about 3 that a visit on a regular daily (sometimes several times a day) basis.
I know my Karma will suffer for this, and I'll be labeled a troll for posting this, but it won't really matter. Reading that last post just made me want to reflect.
That won't happen... In NT, each program runs in their own space. As far as each app is concerned, they have some 4Gigs worth of memory to do what they want.
Zone Alarm was indeed causing BSODs, and serious instability problems. Additionally, in previous beta verison, you had to install BOTH ZA and the MS firewall to completely secure your system. ZA would not prevent incoming traffic, and MS doesn't guard against outbound traffic as well as ZA.
MS is not out to get either of these companies. They are trying to address some of the "security" threats that are out there, and this is a great first step for the novice user.
Except that will open the possibility for trojans to do the same thing... Isn't that what this firewall is supposed to be preventing? Time flies like an arrow;
Actually, check out the video... http://www.microsoft.com/games/gamestock/videos/am ped.avi What impressed me was the trees and how the trees in the distance showed parallex scrolling. That isn't just a pretty background. Everything is rendered realtime, better than anything I've seen on my computer.
Disney has been doing this for quite some time now. A player set to Region 0 has problems, but if you can set your player to any region, it works just fine.
The Divx business model wasn't geared exclusively to the "sales" of the disc. It was geared to the reuse and unlocking of discs. Ultimately this would cost the consumer more, and would require fewer resources. As a business model, that was a sound concept, in practice, consumers were not willing to buy a more expensive player to play regular DVD's, they didn't want to hook up the phone to the player, and other businesses that could distribute the Divx discs wouldn't because the profit margine of being the middle man was so low.
The cost to produce a Divx disc I'm sure was over $1.00, but they hoped to reclaim that in recycled dics and "upgrades".
No, no, no... This is not the case. First of all Command.com is NOT DOS (This is not directed at you, but is a general response to all the inaccurate posts I've seen). It is only the shell. The former IO.SYS and MSDOS.SYS of < Windows 95 were changed to hide DOS. The intent was to remove it then, but this broke to many programs of the time that relied on MSDOS.SYS to be there. The result is that MSDOS.SYS became an INI file with a.SYS extention. This is also why it has to be a certain size as indicated by the blocks of X's at the end of the file. With Me, DOS is completely removed. IO.SYS is nothing more than a loader, but that would be like saying Redhat is still using LILO... can't they get rid of it. IO.SYS does not provide the same funtionality that it used to. Time flies like an arrow;
I've done this, and you don't quite get a Dos prompt... there is infact much more to it as it in turn calls vmm.vxd (I think that is right I did this several months ago) and then you get a dos prompt, BUT it doesn't do you any good. It's really a stupid prompt that doesn't let you do anything better than the EBD, and most importantly, you still can't get it to read config.sys or boot windows from that prompt. This is the problem that I was having with SoftIce. Until NuMega comes out with a newer version, I won't be ussing their debugger. Most companies that are affected by this fundamental change in the way windows handles are already aware of this and need to step up to the plate and make changes or just not support Me. The 9x codebase is dying anyway, so what is the one version that they don't support going to cause? Time flies like an arrow;
No... you are wrong sir... it is not there. Command.com runs on top of Windows to give you a shell, but nothing is loaded at startup now. No config.sys drivers, no autoexec.bat, and no Command.com. Take a good look at the PSP and you'll see that. Time flies like an arrow;
8086: 20 bits of virtual RAM address space (thank you Bill Gates), giving 1Mb maximum RAM. 8bit and 16bit instructions, with an 8bit memory bus. Debut at 4.77Mhz Actually I think you will find Billg had very little to do with that restriction. That was a trade off on address pins on the 8086. A19 was the highest address available on the CPU, not a limitation of the OS... DOS had to work with the architecture, not the otherway around. Secondly the 8086 had a 16bit bus, but the 8088 that IBM used in the XT had an 8bit bus to allow prephrials designed for the 8080 work on the XT, saving them the money from redesigning hardware. 80286: Here is the first example in the x86 range of trying to maintain backwards ISA compatibility... W hile I agree with everything you said here, I think you should also point out that this protected mode in the 80286 is also broken. It just didn't work the way it should, and consequently was rarely used. To be fair, Microsoft tried to design an OS that would support the 80286 in protected mode, the revolutionary Microsoft OS/2. MS and Big Blue had a falling out and IBM kept the name while MS kept the code... expanded and reintroduced in NT. 80386: This was a huge.... Right on par and no major complaints..;) 80486: Incorrperated the 80x87 MPU Pentium: In essence the 80486 with a larger address if I recall, still x86 at heart. Pentium Pro: First Intel line RISC x86 compatible cpu. Pentium II: Pentium Pro without the expensive L2 cache on chip. Funny, but it has very little to do with the Pentium except in namesake Penitum III: Pentium II with extra instructions and finally a Big Brother Serial Number. IA64: Finally moving in the right direction, but slow on the legacy support. Providing an opprotunity for AMD? At any rate it's interesting seeing where things have been and where they are going. Time flies like an arrow;
What I don't like about ASF is how it likes to "lock-up" when it comes across some suspect bits... you advance the time bar, and it will resume... why can't it do that on its own...
As I understand it, Gnutella only asks the hosts your connected to, but they don't know the orgin of who asked. If they don't have the file, they query the hosts they are connected to and so on. I'll attempt to describe this visually.. (Host A) | | | | | \/(Host M) | \ (Host D)-(Host L) \ \\(Host K) \ \/(Host J) \ (Host C)-(Host I) \\(Host H) \/(Host G) (Host B)-(Host F) \(Host E) Now lets pretend that Host G had one of the files I'm looking for and Host J was doing this listing crap. From the protocol, Host G knows that Host B had asked about a file, and tells Host B that either I or another server that I'm connected to has the file or knows where to get it. Host B then tells Host A the same either, I or another server that I'm connected to has the file or knows where to get it. Host J tells Host C the same. So far, the only thing Host J knows is that Host C, or a client connected to Host C, received a request for this file. Host J does not know how many connections away the requesting client is. When you start to download something, maybe this model breaks down then. I don't know if the packets are then sent back over that chain again, or if they are sent directly. As I understand it, Gnutella is designed to protect the identity of both the client and server, so I don't immagine that the IP is anything but the host immediately connected and inquiering. In the case of the above example, Host C. Both the requesting client Host A, and the other server that had the real data, Host G are protected. Time flies like an arrow;
As I understand it, Gnutella only asks the hosts your connected to, but they don't know the orgin of who asked. If they don't have the file, they query the hosts they are connected to and so on.
Now lets pretend that Host G had one of the files I'm looking for and Host J was doing this listing crap. From the protocol, Host G knows that Host B had asked about a file, and tells Host B that either I or another server that I'm connected to has the file or knows where to get it. Host B then tells Host A the same either, I or another server that I'm connected to has the file or knows where to get it.
Host J tells Host C the same. So far, the only thing Host J knows is that Host C, or a client connected to Host C, received a request for this file. Host J does not know how many connections away the requesting client is.
When you start to download something, maybe this model breaks down then. I don't know if the packets are then sent back over that chain again, or if they are sent directly. As I understand it, Gnutella is designed to protect the identity of both the client and server, so I don't immagine that the IP is anything but the host immediately connected and inquiering. In the case of the above example, Host C. Both the requesting client Host A, and the other server that had the real data, Host G are protected. Time flies like an arrow;
Where was there money for My.MP3.com to be made? There is a banner, but I've never even noticed it until just now...:/ If they removed that, then there wouldn't be any revenue from the banners. MP3.com itself _may_ have attracted more attention, and perhaps even gained some additional customers, but I'm not sure the RIAA could prove that. Additionally, I have not given any money to My.MP3.com by using their beem-it software. I don't see how this is in any violation of the law. AFAICT it is a free service offered to me. Time flies like an arrow;
It has to do more with the way the EV6 addresses those processors.
Highspeed ASCII drawing was to be placed here...
This makes the EV6 bus harder to implement, but the advantage is that no CPU needs to wait to access resources. I had tried to draw it for you, but it was a nightmare to make it look right, instead this is a link to the whitepaper on the topic. Page 6 Time flies like an arrow;
I'm surprised no one has answered this yet, but to answer quickly, NO.
The string that is returned goes back a couple of years when your choices in browsers consisted of Mosaic and Mozilla. Mozilla was of course Netscape in its earlier releases. When MICROS~1 designed IE (was there a version before 2.0?) none of the servers would know what MSIE was. Secondly IE more closely resembled Netscape Navigator in the tags that it could parse. Since at the time IE was "compatible" with Netscape, it too adopted Mozilla as it's user-agent string to show that compatibility to the server. Several generations later, many things have changed, but those older legacy portions have remained the same.
Can't do it that way as Napster READS the MP3 to extract the ID3. I'm guess Wrapster fakes that ID info so that it will work through Napster. Time flies like an arrow;
Interesting theory, but this article was first released on Betanews... nothing to do with Slashdot, or even linux for that matter... they have some announcements of some linux beta software, but most of the betas that go through that site are for Windows platforms... Time flies like an arrow;
Literally Apples and Oranges. Different OS's all around. Differnt amounts of memory, no mention of rating. There is much room for improvement on all the systems tested, and ways of bringing them more inline to the same specs. ATI for instance has Rage boards for both the PCs and the MACs. The same amount of memory would also be a good improvement. Same OS for the PCs. Not the best test environment to draw any real conclusions. Time flies like an arrow;
Take a look at Justin's .plan from March 10th. (Thank you google cache) He was working on WASTE then. I think it is safe to say that this was not a hack, and I believe that Justin has the authority for such a release. Gnutella was retractable because the license agreement it was released under allowed for that.
WASTE was released under GPL, and as far as I can tell, it has no such provisions. In fact, it seems to be the contrary. If you accept the agreement, you are given the right to redistribute as long as the GPL is included.
Well, whenever it came online... I KNOW I was a freshman or a sophomore, so that would be late '94 to '96 when I first found it. I've still got a user ID that is 8000 or so. So quite some time ago.
I feel strange writting this, but I can't help but feel the same about the internet as a whole, and even great sites like /. I used to live on this website back in '94/'95 or so, when I first discovered it, and now I just read it every now and then.
Back when my best source of links was Justin's Links from the Underground, and Yahoo hadn't even come on-line yet, I felt as though I'd visited half of the websites out there. Now I only have about 3 that a visit on a regular daily (sometimes several times a day) basis.
I know my Karma will suffer for this, and I'll be labeled a troll for posting this, but it won't really matter. Reading that last post just made me want to reflect.
Good response, "Your NIC is Fsck'd, you should go work for a differnet company." Not the most dedicated employee are you?
/Ryan
That won't happen... In NT, each program runs in their own space. As far as each app is concerned, they have some 4Gigs worth of memory to do what they want.
Zone Alarm was indeed causing BSODs, and serious instability problems. Additionally, in previous beta verison, you had to install BOTH ZA and the MS firewall to completely secure your system. ZA would not prevent incoming traffic, and MS doesn't guard against outbound traffic as well as ZA.
MS is not out to get either of these companies. They are trying to address some of the "security" threats that are out there, and this is a great first step for the novice user.
Except that will open the possibility for trojans to do the same thing... Isn't that what this firewall is supposed to be preventing?
Time flies like an arrow;
Actually, check out the video... http://www.microsoft.com/games/gamestock/videos/am ped.avi What impressed me was the trees and how the trees in the distance showed parallex scrolling. That isn't just a pretty background. Everything is rendered realtime, better than anything I've seen on my computer.
Time flies like an arrow;
Disney has been doing this for quite some time now. A player set to Region 0 has problems, but if you can set your player to any region, it works just fine.
Time flies like an arrow;
The Divx business model wasn't geared exclusively to the "sales" of the disc. It was geared to the reuse and unlocking of discs. Ultimately this would cost the consumer more, and would require fewer resources. As a business model, that was a sound concept, in practice, consumers were not willing to buy a more expensive player to play regular DVD's, they didn't want to hook up the phone to the player, and other businesses that could distribute the Divx discs wouldn't because the profit margine of being the middle man was so low.
The cost to produce a Divx disc I'm sure was over $1.00, but they hoped to reclaim that in recycled dics and "upgrades".
Time flies like an arrow;
No, no, no... This is not the case. First of all Command.com is NOT DOS (This is not directed at you, but is a general response to all the inaccurate posts I've seen). It is only the shell. The former IO.SYS and MSDOS.SYS of < Windows 95 were changed to hide DOS. The intent was to remove it then, but this broke to many programs of the time that relied on MSDOS.SYS to be there. The result is that MSDOS.SYS became an INI file with a .SYS extention. This is also why it has to be a certain size as indicated by the blocks of X's at the end of the file. With Me, DOS is completely removed. IO.SYS is nothing more than a loader, but that would be like saying Redhat is still using LILO... can't they get rid of it. IO.SYS does not provide the same funtionality that it used to.
Time flies like an arrow;
I've done this, and you don't quite get a Dos prompt... there is infact much more to it as it in turn calls vmm.vxd (I think that is right I did this several months ago) and then you get a dos prompt, BUT it doesn't do you any good. It's really a stupid prompt that doesn't let you do anything better than the EBD, and most importantly, you still can't get it to read config.sys or boot windows from that prompt. This is the problem that I was having with SoftIce. Until NuMega comes out with a newer version, I won't be ussing their debugger. Most companies that are affected by this fundamental change in the way windows handles are already aware of this and need to step up to the plate and make changes or just not support Me. The 9x codebase is dying anyway, so what is the one version that they don't support going to cause?
Time flies like an arrow;
No... you are wrong sir... it is not there. Command.com runs on top of Windows to give you a shell, but nothing is loaded at startup now. No config.sys drivers, no autoexec.bat, and no Command.com. Take a good look at the PSP and you'll see that.
Time flies like an arrow;
8086: 20 bits of virtual RAM address space (thank you Bill Gates), giving 1Mb maximum RAM. 8bit and 16bit instructions, with an 8bit memory bus. Debut at 4.77Mhz Actually I think you will find Billg had very little to do with that restriction. That was a trade off on address pins on the 8086. A19 was the highest address available on the CPU, not a limitation of the OS... DOS had to work with the architecture, not the otherway around. Secondly the 8086 had a 16bit bus, but the 8088 that IBM used in the XT had an 8bit bus to allow prephrials designed for the 8080 work on the XT, saving them the money from redesigning hardware. 80286: Here is the first example in the x86 range of trying to maintain backwards ISA compatibility... W hile I agree with everything you said here, I think you should also point out that this protected mode in the 80286 is also broken. It just didn't work the way it should, and consequently was rarely used. To be fair, Microsoft tried to design an OS that would support the 80286 in protected mode, the revolutionary Microsoft OS/2. MS and Big Blue had a falling out and IBM kept the name while MS kept the code... expanded and reintroduced in NT. 80386: This was a huge.... Right on par and no major complaints.. ;) 80486: Incorrperated the 80x87 MPU Pentium: In essence the 80486 with a larger address if I recall, still x86 at heart. Pentium Pro: First Intel line RISC x86 compatible cpu. Pentium II: Pentium Pro without the expensive L2 cache on chip. Funny, but it has very little to do with the Pentium except in namesake Penitum III: Pentium II with extra instructions and finally a Big Brother Serial Number. IA64: Finally moving in the right direction, but slow on the legacy support. Providing an opprotunity for AMD? At any rate it's interesting seeing where things have been and where they are going.
Time flies like an arrow;
ABIT announced this support some time ago... check out the press release from May 5th, 2000
Time flies like an arrow;
What I don't like about ASF is how it likes to "lock-up" when it comes across some suspect bits... you advance the time bar, and it will resume... why can't it do that on its own...
Time flies like an arrow;
To comment on this, please go to this thread where the diagram hasn't been fsck'd by /.'s parser.
Time flies like an arrow;
As I understand it, Gnutella only asks the hosts your connected to, but they don't know the orgin of who asked. If they don't have the file, they query the hosts they are connected to and so on. I'll attempt to describe this visually.. (Host A) | | | | | \/(Host M) | \ (Host D)-(Host L) \ \\(Host K) \ \/(Host J) \ (Host C)-(Host I) \\(Host H) \/(Host G) (Host B)-(Host F) \(Host E) Now lets pretend that Host G had one of the files I'm looking for and Host J was doing this listing crap. From the protocol, Host G knows that Host B had asked about a file, and tells Host B that either I or another server that I'm connected to has the file or knows where to get it. Host B then tells Host A the same either, I or another server that I'm connected to has the file or knows where to get it. Host J tells Host C the same. So far, the only thing Host J knows is that Host C, or a client connected to Host C, received a request for this file. Host J does not know how many connections away the requesting client is. When you start to download something, maybe this model breaks down then. I don't know if the packets are then sent back over that chain again, or if they are sent directly. As I understand it, Gnutella is designed to protect the identity of both the client and server, so I don't immagine that the IP is anything but the host immediately connected and inquiering. In the case of the above example, Host C. Both the requesting client Host A, and the other server that had the real data, Host G are protected.
Time flies like an arrow;
As I understand it, Gnutella only asks the hosts your connected to, but they don't know the orgin of who asked. If they don't have the file, they query the hosts they are connected to and so on.
/(Host M) /(Host J) /(Host G)
I'll attempt to describe this visually..
(Host A)
| | |
| | \
| \ (Host D)-(Host L)
\ \ \(Host K)
\ \
\ (Host C)-(Host I)
\ \(Host H)
\
(Host B)-(Host F)
\(Host E)
Now lets pretend that Host G had one of the files I'm looking for and Host J was doing this listing crap. From the protocol, Host G knows that Host B had asked about a file, and tells Host B that either I or another server that I'm connected to has the file or knows where to get it. Host B then tells Host A the same either, I or another server that I'm connected to has the file or knows where to get it.
Host J tells Host C the same. So far, the only thing Host J knows is that Host C, or a client connected to Host C, received a request for this file. Host J does not know how many connections away the requesting client is.
When you start to download something, maybe this model breaks down then. I don't know if the packets are then sent back over that chain again, or if they are sent directly. As I understand it, Gnutella is designed to protect the identity of both the client and server, so I don't immagine that the IP is anything but the host immediately connected and inquiering. In the case of the above example, Host C. Both the requesting client Host A, and the other server that had the real data, Host G are protected.
Time flies like an arrow;
Where was there money for My.MP3.com to be made? There is a banner, but I've never even noticed it until just now... :/ If they removed that, then there wouldn't be any revenue from the banners. MP3.com itself _may_ have attracted more attention, and perhaps even gained some additional customers, but I'm not sure the RIAA could prove that. Additionally, I have not given any money to My.MP3.com by using their beem-it software. I don't see how this is in any violation of the law. AFAICT it is a free service offered to me.
Time flies like an arrow;
Is a codec by that name, not the CC fiasco.
Time flies like an arrow;
Time flies like an arrow;
I'm surprised no one has answered this yet, but to answer quickly, NO.
The string that is returned goes back a couple of years when your choices in browsers consisted of Mosaic and Mozilla. Mozilla was of course Netscape in its earlier releases. When MICROS~1 designed IE (was there a version before 2.0?) none of the servers would know what MSIE was. Secondly IE more closely resembled Netscape Navigator in the tags that it could parse. Since at the time IE was "compatible" with Netscape, it too adopted Mozilla as it's user-agent string to show that compatibility to the server. Several generations later, many things have changed, but those older legacy portions have remained the same.
Time flies like an arrow;
Can't do it that way as Napster READS the MP3 to extract the ID3. I'm guess Wrapster fakes that ID info so that it will work through Napster.
Time flies like an arrow;
Interesting theory, but this article was first released on Betanews... nothing to do with Slashdot, or even linux for that matter... they have some announcements of some linux beta software, but most of the betas that go through that site are for Windows platforms...
Time flies like an arrow;
Literally Apples and Oranges. Different OS's all around. Differnt amounts of memory, no mention of rating. There is much room for improvement on all the systems tested, and ways of bringing them more inline to the same specs. ATI for instance has Rage boards for both the PCs and the MACs. The same amount of memory would also be a good improvement. Same OS for the PCs. Not the best test environment to draw any real conclusions.
Time flies like an arrow;