Just remember, any PowerPC based Mac, which is just about any Mac made after 1994 with four digits in the model number or any of the Macs made after 1997 with no model number, running MacOS 7.5.5, which was released in 1996, or newer can use logical drives up to 2 TB. You would probably want to use MacOS 8.1 and HFS+ because if you use an older version of MacOS you will be forced to use HFS standard. Due to a limitation with HFS standard, with a 2TB volume the smallest file size would be 32MB. On a hypothetical 2TB HFS standard volume even if the file contained the letter "a" it would still be 32MB. On the other hand it would take a good deal of engineering and coding to even approach 2TB of storage on a 6200 which only has narrow SCSI, supports only one IDE drive and has only a 68030 PDS slot for expansion. Or for that matter why you would want to do it on a 6500 which at least has two PCI slots, but will not work with PCI to PCI bridge chips due to ROM bugs. The maximum amount of RAM the 6500 can use is 128 MB without some serious soldering and then even the theoretical max would be 192MB, not that I have ever heard of anyone doing this. I guess what I am saying is that the 6500 would make a poor choice for a server of a very large database .
Well I don't know, it's snowing very heavily in the Twin Cities in Minnesota right now and that's not any kind of April Fools joke. The Twin Cities area is looking at anywhere from an inch to two inches and the northeastern part of town is looking at up to four inches. My guess is that the Twin Cities will end up with more than that. Needless to say this is unusual even for the Twin Cities.
Another fun thing to do would be writing an obfucated program in MacOS 9 with self modifying code that mixed 68k assembly functions with PPC assembly functions.
Aside from the x86 architecture, the PCI bus and a few odd bi-endian PPCs(hmm) I don't think that there much else out there that is little-endian. One might even wonder if little-endian should be called "Intel Fag" mode.
Qwest has been charged by the Minnesota Department of Commerce with entering into secret deals that worked to the disadvantage of its local competetion. If Qwest did this, it merrily violated state and federal laws forcing Qwest to make these sorts of deals fair, non-discriminatory and to file these agreements with the Minnesota PUC. According to the charges Qwest has done none of these. If the Minnesota PUC rules against Qwest, Qwest could be looking at a fine from anywhere between $56 million to $202 million for this activity.
Or to save some dead trees have another computer not hooked up to any network connected to a serial port on the firewall. The firewall would then direct all logging activity to this serial port. The logging machine would then direct all input from the firewall into a file. That way you could save yourself many sheets of paper.
There is an even more lazy technique than the one you mentioned assuming both machines have Firewire and at least one of the machines is an AGP graphics G4, iBook, Powerbook G3 Firewire, or Titanium G4 Powerbook. With both boxes off, hook a 6-pin to 6-pin Firewire cable between the two Macs. Turn the power on on one and press and hold the "T" key. Wait until a white screen with an icon appears. You have now entered "Firewire Target Disk Mode." Turn the other computer on. Wait until the second computer starts up normally and observe the first computer's hard drive mounting on the second. Congratulations, you now have a large boxy firewire drive. Copy what files you want to the new computer. Unmount the first computer's volume on the second and press the power button on the first. Disconnect the Firewire cable. You are now done. I've done this before. I really really like using this method.
Open Firmware is pretty neat you can telnet into it from a remote computer and you can net boot from it too. One of the other neat features of Open Firmware is that it is architecture independent so a video card or a SCSI card for a Mac would also initialized properly on a Sun. Of course driver support in the OS is a totally different issue.
Reminds me of Driver. Apparently if one car in a collision lands on top of the other, it will fly up with much more kinetic energy than the two car system had before. Once when I was playing a car managed to land on the hood of another car and bounced what would have been 100 feet into the air then to top it off it landed on the hood of a second car and flew what would have been even farther and higher, assuming that the game had not ended before it started to lose altitude. I do not think that the gravity was particularly low on Driver, but when one car lands on the hood of another there will certainly be some flying going on.
IIRC the Powerbook G3 Firewire, aka Pismo also uses the same processor socket as the G4 Tower and Cube. Mmm, a dual processor laptop, what could be better? Or what could be warmer? Anyone want to guess how much power the laptop would draw like that? I wonder how long the battery would last on such a beast?
Then again you have the other extreme. Lets put the processor card from the Powerbook G3 in a G4 Cube and see how long it would take before the victim noticed.
Here's some more Microsoft EULA stupidity. You can only run IE 5.0 for Mac on the OS it was intended to be run on. So potentially no Wine-like implementations of the MacOS API calls could run IE 5.0 on Linux or *BSD according to the EULA. Not that Mac on Linux would be affected by this since you are running the MacOS.
Don't tempt me. Also to produce X-rays like that you would somehow have to defeat the X-ray protection circuit. Not impossible just harder to do. Another great thing to concentrate those X-rays would be to unplug or remove the vertical and horizontal deflection coils and fix some of the other components so there is no more vertical or horizintal deflection that occurs in the monitor. The electron beam would then come out as a point on the screen. Which would be great fun as long as you were at least a half mile away when you turned the monitor on.
Mmm rad-hardened PPC 750 boards. I'm guessing that these don't have backside cache and are actually 740s. That's besides the point. Imagine if you will, a Beowulf cluster in orbit around Jupiter. I'm not sure what you could do with it but in the ~10 years it would take to get there I'm sure you could think of something.
Now whose numbers are those "45-55%" from, how were they gathered, how old are they and what were their methodology? Were thewse numbers from a conservative think-tank, done 6 years ago, done using push polling and were the loosest standards for "conservative" used? If so that is a useless number. I'd look at the latest elections, Gore won the popular vote, the Democrats control the Senate and control of the House is slowly slipping though the fingers of the Republicans. Getting back on topic, in the polls I heard 60% of those polled were for stem cell research.
If only that were true, if only that were true. Apparently you have never tried to terminate the SCSI chain on old Macs. I have had to deal with chains that work fine on an old Mac clone and the same chain would refuse to work on an Apple Mac. Also Apple put crap terminators in PowerBooks that were insufficient for any more than one external device. Any more than that and you were asking for trouble. Doing so was an ideal time to sacrifice a goat to your favorite deity/demonic entity. There is also the whole terrifying experience of the O'Hare SCSI controller. I guess at Apple was thinking: "Let's package IDE, serial, and SCSI into one ASIC for our new laptop, and make the SCSI part of the ASIC just like the old MESH SCSI chip." Now that was a very bad idea. First off Apple had only designed a barely passable Fast SCSI controller that hung rather ridiculously off of the I/O controller on its own bus instead of off of the PCI bus. Additionally the MESH controller is picky about termination even when used internally. On top of that the MESH controller on O'Hare is run at Slow SCSI speeds. Just to throw into mix there is a hardware-timing bug that shows up with some scanners. Next some Einstein decided to share the love and put the O'Hare controller in desktop computers and leave them unterminated on the motherboard, but put a terminator right after the internal SCSI CR-ROM. Yes, some of these machines had a SCSI CD-ROM drive, but an IDE internal hard drive. What was really scary was that there were some with both an IDE CD-ROM and hard drive, which was achieved by making them both master drives on the same bus. These machines are actually more stable when you put a terminator on the external SCSI port regardless of whether or not there are any external devices connected.
Hey don't forget that PCI based Macs and most PCI based PPC machines use Forth. IIRC the boot ROM for such devices as video cards, mass storage cards and other PCI cards that need to be dealt with before the OS is loaded are also written in Forth. BTW has anyone ever tried to put a PCI card with boot ROMs intended for a Mac into an UltraSPARC and seen if it works?
Reminds me of a wierded out episode of some wierd early nineties Disney cartoon whose name I can't remember where Novembria, a nation sort of like the USSR used cast iron bathtubs instead of explosive bombs.
You can get both a million volts and a million amps out of a single AA battery, just not for very long. To get it a million volts and amps for the longest amount of time you would probably have to use a lithium ion battery. Additionally, you would also need an inductor and a capacitor. Just don't be near me when you try this. For starters you would have to defeat some basic safety mechanisms on the battery. Drawing that much current that fast would make the battery explode. Molten lithium and molten lithium hydroxide are not fun. You'd also get some terrible arcing unless you used the right components. All and all this would not be a good idea.
You apparently have never tried to boot VMS off of a SCSI drive over 1.2GB on a VAX. Or for that matter any drive larger than 2GB on a 68K Mac. The machines will puke. Also for that sparcstation make sure you have that 180GB drive well cooled. There is nothing quite like spending $2000 on a drive including controller card and having it fail in six months. The moment I can justify spending over five times per GB for something inherently less reliable and not appreciably faster I'll talk to you. I don't know about you but I know four 7.2k 75GB IDE doing RAID 0 (striping if you didn't know) are always going to be faster than one 180GB Ultra160 even in an Adaptec 29160 in a 64 bit PCI slot. Oh wait a minute there are no consumer grade PCs with 64 bit PCI slots. In the mean time I'll deal with the inevitable delays with a standards process.
Hmm, too bad there was no way that I could have gotten to MacHack. Earlier this year I transplanted the ADB controller from one of those Apple mice shaped like that into a 3 button PS/2 mouse from Digital of about the same age. I also hacked up a copy of the Mouse Key control panel from Logitech so that Mouse Key would recognize the "new" three button mouse. I really only got away with it because both mice were manufactured by Logitech and their controllers both essentially had the same pin outs. I had to hack up Mouse Key because it was designed to only recognize ADB devices with certain ADB IDs, I just replaced the IDs for one of the Logitech mice with the ID from the Apple mouse. Oddly enough this was the hardest part. I did this all before I realized that I could have used the disassembler for ResEdit and it would have been easier. The only problem is that Mouse Key thinks that the right button is the middle button and the middle button the right. This is probably my fault, but I could easily fix that by using a different Logitech Mouse ID.
This "You can only play our way" is not very new. At least in MSIE 5 for "MacOS classic" the EULA states that you can only use MSIE in the OS it was intended for. Now I have never read the EULA for MSIE for Windows, but I'm guessing that it has a similar statement. My understanding is that this shoots down anyone trying to use MSIE in Linux under WINE. IANAL, but WINE could be considered emulation, and since emulation is legal I seriously doubt that Microsoft has a leg to stand on, but this has never stopped Microsoft before and probably never will.
Now that would be something to see, a firewire keyboard and mouse.
Just remember, any PowerPC based Mac, which is just about any Mac made after 1994 with four digits in the model number or any of the Macs made after 1997 with no model number, running MacOS 7.5.5, which was released in 1996, or newer can use logical drives up to 2 TB.
You would probably want to use MacOS 8.1 and HFS+ because if you use an older version of MacOS you will be forced to use HFS standard. Due to a limitation with HFS standard, with a 2TB volume the smallest file size would be 32MB. On a hypothetical 2TB HFS standard volume even if the file contained the letter "a" it would still be 32MB.
On the other hand it would take a good deal of engineering and coding to even approach 2TB of storage on a 6200 which only has narrow SCSI, supports only one IDE drive and has only a 68030 PDS slot for expansion. Or for that matter why you would want to do it on a 6500 which at least has two PCI slots, but will not work with PCI to PCI bridge chips due to ROM bugs. The maximum amount of RAM the 6500 can use is 128 MB without some serious soldering and then even the theoretical max would be 192MB, not that I have ever heard of anyone doing this. I guess what I am saying is that the 6500 would make a poor choice for a server of a very large database .
You realize that there's not a whole lot worth "buffering" in Georgia, bucko.
Well I don't know, it's snowing very heavily in the Twin Cities in Minnesota right now and that's not any kind of April Fools joke. The Twin Cities area is looking at anywhere from an inch to two inches and the northeastern part of town is looking at up to four inches. My guess is that the Twin Cities will end up with more than that. Needless to say this is unusual even for the Twin Cities.
That's okay, they probably are the same person.
Another fun thing to do would be writing an obfucated program in MacOS 9 with self modifying code that mixed 68k assembly functions with PPC assembly functions.
Aside from the x86 architecture, the PCI bus and a few odd bi-endian PPCs(hmm) I don't think that there much else out there that is little-endian. One might even wonder if little-endian should be called "Intel Fag" mode.
Perhaps you've never heard of the next door neighbor city to Kansas City, Missouri, Kansas City, Kansas. Idiot.
Or the big telco companies could do what Qwest in Minnesota has been charged with.
m l
According to this article:
http://www.startribune.com/stories/535/1626045.ht
Qwest has been charged by the Minnesota Department of Commerce with entering into secret deals that worked to the disadvantage of its local competetion. If Qwest did this, it merrily violated state and federal laws forcing Qwest to make these sorts of deals fair, non-discriminatory and to file these agreements with the Minnesota PUC. According to the charges Qwest has done none of these. If the Minnesota PUC rules against Qwest, Qwest could be looking at a fine from anywhere between $56 million to $202 million for this activity.
Or to save some dead trees have another computer not hooked up to any network connected to a serial port on the firewall. The firewall would then direct all logging activity to this serial port. The logging machine would then direct all input from the firewall into a file. That way you could save yourself many sheets of paper.
There is an even more lazy technique than the one you mentioned assuming both machines have Firewire and at least one of the machines is an AGP graphics G4, iBook, Powerbook G3 Firewire, or Titanium G4 Powerbook. With both boxes off, hook a 6-pin to 6-pin Firewire cable between the two Macs. Turn the power on on one and press and hold the "T" key. Wait until a white screen with an icon appears. You have now entered "Firewire Target Disk Mode." Turn the other computer on. Wait until the second computer starts up normally and observe the first computer's hard drive mounting on the second. Congratulations, you now have a large boxy firewire drive. Copy what files you want to the new computer. Unmount the first computer's volume on the second and press the power button on the first. Disconnect the Firewire cable. You are now done. I've done this before. I really really like using this method.
Open Firmware is pretty neat you can telnet into it from a remote computer and you can net boot from it too. One of the other neat features of Open Firmware is that it is architecture independent so a video card or a SCSI card for a Mac would also initialized properly on a Sun. Of course driver support in the OS is a totally different issue.
Reminds me of Driver. Apparently if one car in a collision lands on top of the other, it will fly up with much more kinetic energy than the two car system had before. Once when I was playing a car managed to land on the hood of another car and bounced what would have been 100 feet into the air then to top it off it landed on the hood of a second car and flew what would have been even farther and higher, assuming that the game had not ended before it started to lose altitude. I do not think that the gravity was particularly low on Driver, but when one car lands on the hood of another there will certainly be some flying going on.
IIRC the Powerbook G3 Firewire, aka Pismo also uses the same processor socket as the G4 Tower and Cube. Mmm, a dual processor laptop, what could be better? Or what could be warmer? Anyone want to guess how much power the laptop would draw like that? I wonder how long the battery would last on such a beast?
Then again you have the other extreme. Lets put the processor card from the Powerbook G3 in a G4 Cube and see how long it would take before the victim noticed.
Here's some more Microsoft EULA stupidity. You can only run IE 5.0 for Mac on the OS it was intended to be run on. So potentially no Wine-like implementations of the MacOS API calls could run IE 5.0 on Linux or *BSD according to the EULA. Not that Mac on Linux would be affected by this since you are running the MacOS.
Don't tempt me. Also to produce X-rays like that you would somehow have to defeat the X-ray protection circuit. Not impossible just harder to do. Another great thing to concentrate those X-rays would be to unplug or remove the vertical and horizontal deflection coils and fix some of the other components so there is no more vertical or horizintal deflection that occurs in the monitor. The electron beam would then come out as a point on the screen. Which would be great fun as long as you were at least a half mile away when you turned the monitor on.
Mmm rad-hardened PPC 750 boards. I'm guessing that these don't have backside cache and are actually 740s. That's besides the point. Imagine if you will, a Beowulf cluster in orbit around Jupiter. I'm not sure what you could do with it but in the ~10 years it would take to get there I'm sure you could think of something.
Now whose numbers are those "45-55%" from, how were they gathered, how old are they and what were their methodology? Were thewse numbers from a conservative think-tank, done 6 years ago, done using push polling and were the loosest standards for "conservative" used? If so that is a useless number. I'd look at the latest elections, Gore won the popular vote, the Democrats control the Senate and control of the House is slowly slipping though the fingers of the Republicans. Getting back on topic, in the polls I heard 60% of those polled were for stem cell research.
If only that were true, if only that were true. Apparently you have never tried to terminate the SCSI chain on old Macs. I have had to deal with chains that work fine on an old Mac clone and the same chain would refuse to work on an Apple Mac. Also Apple put crap terminators in PowerBooks that were insufficient for any more than one external device. Any more than that and you were asking for trouble. Doing so was an ideal time to sacrifice a goat to your favorite deity/demonic entity. There is also the whole terrifying experience of the O'Hare SCSI controller. I guess at Apple was thinking: "Let's package IDE, serial, and SCSI into one ASIC for our new laptop, and make the SCSI part of the ASIC just like the old MESH SCSI chip." Now that was a very bad idea. First off Apple had only designed a barely passable Fast SCSI controller that hung rather ridiculously off of the I/O controller on its own bus instead of off of the PCI bus. Additionally the MESH controller is picky about termination even when used internally. On top of that the MESH controller on O'Hare is run at Slow SCSI speeds. Just to throw into mix there is a hardware-timing bug that shows up with some scanners. Next some Einstein decided to share the love and put the O'Hare controller in desktop computers and leave them unterminated on the motherboard, but put a terminator right after the internal SCSI CR-ROM. Yes, some of these machines had a SCSI CD-ROM drive, but an IDE internal hard drive. What was really scary was that there were some with both an IDE CD-ROM and hard drive, which was achieved by making them both master drives on the same bus. These machines are actually more stable when you put a terminator on the external SCSI port regardless of whether or not there are any external devices connected.
Hey don't forget that PCI based Macs and most PCI based PPC machines use Forth. IIRC the boot ROM for such devices as video cards, mass storage cards and other PCI cards that need to be dealt with before the OS is loaded are also written in Forth. BTW has anyone ever tried to put a PCI card with boot ROMs intended for a Mac into an UltraSPARC and seen if it works?
Reminds me of a wierded out episode of some wierd early nineties Disney cartoon whose name I can't remember where Novembria, a nation sort of like the USSR used cast iron bathtubs instead of explosive bombs.
You can get both a million volts and a million amps out of a single AA battery, just not for very long. To get it a million volts and amps for the longest amount of time you would probably have to use a lithium ion battery. Additionally, you would also need an inductor and a capacitor. Just don't be near me when you try this. For starters you would have to defeat some basic safety mechanisms on the battery. Drawing that much current that fast would make the battery explode. Molten lithium and molten lithium hydroxide are not fun. You'd also get some terrible arcing unless you used the right components. All and all this would not be a good idea.
You apparently have never tried to boot VMS off of a SCSI drive over 1.2GB on a VAX. Or for that matter any drive larger than 2GB on a 68K Mac. The machines will puke. Also for that sparcstation make sure you have that 180GB drive well cooled. There is nothing quite like spending $2000 on a drive including controller card and having it fail in six months. The moment I can justify spending over five times per GB for something inherently less reliable and not appreciably faster I'll talk to you. I don't know about you but I know four 7.2k 75GB IDE doing RAID 0 (striping if you didn't know) are always going to be faster than one 180GB Ultra160 even in an Adaptec 29160 in a 64 bit PCI slot. Oh wait a minute there are no consumer grade PCs with 64 bit PCI slots. In the mean time I'll deal with the inevitable delays with a standards process.
Hmm, too bad there was no way that I could have gotten to MacHack. Earlier this year I transplanted the ADB controller from one of those Apple mice shaped like that into a 3 button PS/2 mouse from Digital of about the same age. I also hacked up a copy of the Mouse Key control panel from Logitech so that Mouse Key would recognize the "new" three button mouse. I really only got away with it because both mice were manufactured by Logitech and their controllers both essentially had the same pin outs. I had to hack up Mouse Key because it was designed to only recognize ADB devices with certain ADB IDs, I just replaced the IDs for one of the Logitech mice with the ID from the Apple mouse. Oddly enough this was the hardest part. I did this all before I realized that I could have used the disassembler for ResEdit and it would have been easier. The only problem is that Mouse Key thinks that the right button is the middle button and the middle button the right. This is probably my fault, but I could easily fix that by using a different Logitech Mouse ID.
This "You can only play our way" is not very new. At least in MSIE 5 for "MacOS classic" the EULA states that you can only use MSIE in the OS it was intended for. Now I have never read the EULA for MSIE for Windows, but I'm guessing that it has a similar statement. My understanding is that this shoots down anyone trying to use MSIE in Linux under WINE. IANAL, but WINE could be considered emulation, and since emulation is legal I seriously doubt that Microsoft has a leg to stand on, but this has never stopped Microsoft before and probably never will.