Not all, but most of the G4 lineup is. I have an AGP graphics G4 that was a 400 MHz G4 and can be upgraded to a dual cpu daughtercard from GigaDesign, sonnet, or a similar company.
The dual cpu G4's can have two cpu's on a single daughtercard even though there are two separate daughtercard sockets. You just leave one of them empty. As long as you have a UniNorth rev 7 or later you can run multiprocessor. I do believe that two cpu's is the limit for some reason. I don't think you can have two dual cpu daughtercards, I'm not sure I remember why.
Or you could use NetBSD/macppc and have SMP, more hardware support, more device support, no services enabled by default, and Linux/FreeBSD/Darwin binary emulation.
There seems to be some trouble at Verio or ISC with the main NetBSD site. I've had no trouble getting to it through Pair.com's mirror www3.us.netbsd.org.
Um, not really. OS X isn't BSD, it's Mach with a BSD subsystem on top of it. Apple's mach servers power the interface and native GUI applications while the BSD system typically runs daemons. It's a hybrid that works very well, with the exception of GUI tools controlling daemon config files. There needs to be a lot of polishing done there.
Yes, several of our gateways Pentium II's came with "heated" Microsoft PS/2 Intellimice. Unfortunately the darn things kept melting and nearly catching fire, or just stop working. You'd think they would test this stuff before you introduce a product that nobody else has. Sheesh.
As for heated keyboards, I suggest some toaster wire and a variac, or the PowerBook G3 Wallstreet, Mainstreet, or PDQ models. All of which use the back of the keyboard as a heat pipe from the CPU heatsink. (That said, it's a very solid machine.)
Softdeps != journaling, of course journaling is going to win vs. soft deps. Duh.
RAIDframe still has a ways to go
Default file system creation options for NetBSD ffs are far from optimal on high power systems. Tweaking those would probably give a significant performance boost, with or without softdeps.
BSD developers typically do not sacrifice portability for speed. It was not so long ago that Linux distros had async file I/O on ext2 without journaling. Naturally async is going to be faster than the default safer sync option on ffs.
Obviously, because it's good for you the customer and bad for them. The media moguls would have a much harder time telling you what to think and do on every channel, among other reasons.
"Never again pay for a service that would be dirt cheap - if it weren't run by a bunch of profiteering gluttons." - Hackers.
Re:In case developers didn't get the clue:
on
GNOME 2.6 Reviewed
·
· Score: 0, Offtopic
The humiliating failure of the Apple Newton put mobile computers on hold for a few years, until Palm revitalized the once dead market.
I suggest you read the book Defying Gravity before you believe what you've heard.
Off the top of my head from the text: The Newtons handwriting recognition was fine. The problem was that Apple sent out protype test units that did not have functional handwriting recognition as demos to retailers. While this was the fatal mistake that tarnished the entire project, these faulty units should never have seen the light of day. The media simply latched on to this and never let it go. Probably writers and publishers on microsofts payroll to prevent a truely innovative product from taking hold.
They also say that Apple's unveilings of the newton to the press and at macworld were done with hypercard showing on the newton screen. Was this a mistake, yes. But, the actual production units were not done. The book does a very good job of explaining it.
No matter what the media says, the Newton, eMate, and Message Pad were all solid, innovative devices. Ask anyone who's used the real thing and they'll tell you it does as much as todays PDAs minus the cameras, mp3s and video. They were even trying to get a wireless internet standard off the ground in 1995.
Its also interesting to note that the AT&T Hobbit chipset was developed by the Newton team, then later abandoned and then was quickly snapped up by competition.
Old World machines do not have flashable chips. You would have to unsolder the apple chips from the ROM DIMM and/or motherboard and replace them with something that is electronically eraseable.
FreeBIOS seems like a better choice.
The only reason mac pci cards are more expensive is because vendors CAN charge 4x as much and people will still pay it as not enough companies make it
Why mess with the system rom and option card rom at all? Unless you want to use your x86 SCSI or vGA card during the boot process where the firmware has control or to boot from them its not needed. set openfirmware to serial console and fire up X when you get to multiuser. Snootchie bootchies. There's no requirement of x86 nor open firmware fcode to use a card once the kernel is booted.
The larger problem is card makers cannot be bothered to do it right the first time. Hardware is often made to operate in either endian, if the card makers weren't spending all their time debugging obscure x86 BIOS issues they could probably spend a few hours and add fcode so it could work on Sun and Apple hardware.
I'm pretty sure there's a Linux VAX tree. Yes NetBSD counts atari and amiga as separate ports. It helps reduce confusion. There's a base port called m68k which has branches from it like mac68k, mvme68k, etc. Just as powerpc has macppc, ofppc, prep, etc. It's really not that hard to grok.
Apple did not focus on paint programs, they focused on the user experience. I guess you've never heard of ClarisWorks, Appleworks, PageMaker, Works, FileMaker, FoxPro, and the other microsoft office programs. Operating system manufacturers don't "focus" on the software other companies write for their platform, other companies choose not to write for a particular platform. Apple doesn't go around convincing companies to write programs for them. That argument is silly.
Yes localtalk is slower than 10Base2 or 10Base5, do you know how much an ISA network card cost for the IBM PC at the time? $500 or more, and they were hardly reliable. Endless support problems? How about when one of the 10base2 network had a problem? The entire network end to end went down as well. Where's the magical difference? If you mean going to the computer seeing that it's unplugged and plugging it back in is worse than straining the 10baseX connector until the wire, connector, or card broke or was intermittently bad, I guess LocalTalk is worse.
Microsoft did not build NT from the ground up. NT started on the MIPS R4000 with help from DEC's OSIX, OSF/1, BSD, and VMS. I believe all of which were written in C before microsoft started writing windows in vi on Xenix. NT wasn't released until 96.
Near the same time, DEC turned down Apple when Apple approached DEC about jumping ship from 680x0 to the Alpha processor. The only reason Apple jumped to PowerPC was because "DEC couldn't bring itself to work with Apple." No doubt due to Microsoft pulling strings to prevent Apple from getting into the platform that would probably have crushed Intel/Microsoft desktop dominance, had Intel not stollen designs from the Alpha processor group and inserted them into the Pentium II. Notice how NT/XP/2k/2k3 use ARC boot syntax in boot.ini from Alpha ARC BIOS or how closely ComDECpaqHP is with microsoft?
Oh, and while you're going to bash apple for running 68k code in emulation on PowerPC, At least Apple gave you something that worked, as slow as it was. I guess microsoft and intel never emulated anything, that wowexec program must just be for show. And all that microcode in the CPU, there's no emulation there!
Apple never tried to get out of the current trend of things or anything: MkLinux, Copeland, AIX, Rhapsody. They couldn't convince their user base to jump ship to a new platform or operating system without the applications already in place, and nobody wanted to write for Windows and MacOS as it was. Is it a problem yes, but hardly an apple specific one.
"Imagine using a machine that didn't have virtual memory and ran out of memory [if you didn't have enough]..." Imagine using a machine where nobody will ever need more than 640k, nobody will ever need more than 15 IRQs, nobody will ever need more than 3 DMA channels, nobody will ever need more than one MFM/RLL hard drive controller, nobody will ever need more than one VGA card, all cards will run at 8.3MHz for all eternity, all cards and BIOS's will be ISAPnP, all CPUs will be genuine Intel, there will always be enough conventional memory, and all drivers run in real mode and there will never be any conflicts.
Guess who was writing the "business" programs for Apple when they started out with Macintosh? Your good buddy microsoft [and Aldus/Adobe].
"But Windows caught up and overtook the Macintosh, both in terms of user interface and developer tools." Yeah, inventing your own closed, proprietary APIs at every turn and forcing everyone to use them didn't have anything to do with that. DirectX, ActiveX, COM/COM+/DCOM, SMB/CIFS, DirectDraw, Direct3D, DirectInput, Microsoft JVM, Internet Exploder, Exchange, NTFS, etc. All competeing with already existing standards, but rather than implement them, we'll make an incompatible, competing version of it, not tell anyone how it works, and cause more diversion to increase lock in while we're at it. You won't be a good microsoft zombie if you write code for anyone other than them or use something that actually follows a real standard rather than microsofts deliberately poor implementation of it.
Slashdot Mirror
google search for IBM XL G5.
The dual cpu G4's can have two cpu's on a single daughtercard even though there are two separate daughtercard sockets. You just leave one of them empty. As long as you have a UniNorth rev 7 or later you can run multiprocessor. I do believe that two cpu's is the limit for some reason. I don't think you can have two dual cpu daughtercards, I'm not sure I remember why.
There are several other sites as well. http://k26.com/buran/ and http://www.buran.ru/ are the two I have visited so far.
-n Do not flush the file system cache. This option should be used with extreme caution. It can be used if a disk or the processor is on fire.
lol.
Or you could use NetBSD/macppc and have SMP, more hardware support, more device support, no services enabled by default, and Linux/FreeBSD/Darwin binary emulation.
or NetBSD's pkgsrc.
In Soviet Russia, G5 makes IBM!
There seems to be some trouble at Verio or ISC with the main NetBSD site. I've had no trouble getting to it through Pair.com's mirror www3.us.netbsd.org.
They have to pay the lobbyists with something
If by destroyed you mean violated their agreement with DEC and copied parts of the chip design of the Alpha into the Pentium II, then yes.
Really? Were they available in 1994 too?
Yes, they "fixed" this by giving LAN cards a GUID and the BIOS some kind of serial number didn't they?
Um, not really. OS X isn't BSD, it's Mach with a BSD subsystem on top of it. Apple's mach servers power the interface and native GUI applications while the BSD system typically runs daemons. It's a hybrid that works very well, with the exception of GUI tools controlling daemon config files. There needs to be a lot of polishing done there.
Yes, several of our gateways Pentium II's came with "heated" Microsoft PS/2 Intellimice. Unfortunately the darn things kept melting and nearly catching fire, or just stop working. You'd think they would test this stuff before you introduce a product that nobody else has. Sheesh.
As for heated keyboards, I suggest some toaster wire and a variac, or the PowerBook G3 Wallstreet, Mainstreet, or PDQ models. All of which use the back of the keyboard as a heat pipe from the CPU heatsink. (That said, it's a very solid machine.)
that people forgot about 3Dfx Glide? :)
Better yet, where is an updated StarTac?
they could make the keys partly translucent and add a backlight...
Obviously, because it's good for you the customer and bad for them. The media moguls would have a much harder time telling you what to think and do on every channel, among other reasons.
"Never again pay for a service that would be dirt cheap - if it weren't run by a bunch of profiteering gluttons." - Hackers.
Perhaps I'm not the only one who feels this way.
Or, you could just go to google and type mach 10 in mph in the search box and hit return.
I suggest you read the book Defying Gravity before you believe what you've heard.
Off the top of my head from the text: The Newtons handwriting recognition was fine. The problem was that Apple sent out protype test units that did not have functional handwriting recognition as demos to retailers. While this was the fatal mistake that tarnished the entire project, these faulty units should never have seen the light of day. The media simply latched on to this and never let it go. Probably writers and publishers on microsofts payroll to prevent a truely innovative product from taking hold.
They also say that Apple's unveilings of the newton to the press and at macworld were done with hypercard showing on the newton screen. Was this a mistake, yes. But, the actual production units were not done. The book does a very good job of explaining it.
No matter what the media says, the Newton, eMate, and Message Pad were all solid, innovative devices. Ask anyone who's used the real thing and they'll tell you it does as much as todays PDAs minus the cameras, mp3s and video. They were even trying to get a wireless internet standard off the ground in 1995.
Its also interesting to note that the AT&T Hobbit chipset was developed by the Newton team, then later abandoned and then was quickly snapped up by competition.
FreeBIOS seems like a better choice.
The only reason mac pci cards are more expensive is because vendors CAN charge 4x as much and people will still pay it as not enough companies make it
Why mess with the system rom and option card rom at all? Unless you want to use your x86 SCSI or vGA card during the boot process where the firmware has control or to boot from them its not needed. set openfirmware to serial console and fire up X when you get to multiuser. Snootchie bootchies. There's no requirement of x86 nor open firmware fcode to use a card once the kernel is booted.
The larger problem is card makers cannot be bothered to do it right the first time. Hardware is often made to operate in either endian, if the card makers weren't spending all their time debugging obscure x86 BIOS issues they could probably spend a few hours and add fcode so it could work on Sun and Apple hardware.
I'm pretty sure there's a Linux VAX tree. Yes NetBSD counts atari and amiga as separate ports. It helps reduce confusion. There's a base port called m68k which has branches from it like mac68k, mvme68k, etc. Just as powerpc has macppc, ofppc, prep, etc. It's really not that hard to grok.
Apple did not focus on paint programs, they focused on the user experience. I guess you've never heard of ClarisWorks, Appleworks, PageMaker, Works, FileMaker, FoxPro, and the other microsoft office programs. Operating system manufacturers don't "focus" on the software other companies write for their platform, other companies choose not to write for a particular platform. Apple doesn't go around convincing companies to write programs for them. That argument is silly.
Yes localtalk is slower than 10Base2 or 10Base5, do you know how much an ISA network card cost for the IBM PC at the time? $500 or more, and they were hardly reliable. Endless support problems? How about when one of the 10base2 network had a problem? The entire network end to end went down as well. Where's the magical difference? If you mean going to the computer seeing that it's unplugged and plugging it back in is worse than straining the 10baseX connector until the wire, connector, or card broke or was intermittently bad, I guess LocalTalk is worse.
Microsoft did not build NT from the ground up. NT started on the MIPS R4000 with help from DEC's OSIX, OSF/1, BSD, and VMS. I believe all of which were written in C before microsoft started writing windows in vi on Xenix. NT wasn't released until 96.
Near the same time, DEC turned down Apple when Apple approached DEC about jumping ship from 680x0 to the Alpha processor. The only reason Apple jumped to PowerPC was because "DEC couldn't bring itself to work with Apple." No doubt due to Microsoft pulling strings to prevent Apple from getting into the platform that would probably have crushed Intel/Microsoft desktop dominance, had Intel not stollen designs from the Alpha processor group and inserted them into the Pentium II. Notice how NT/XP/2k/2k3 use ARC boot syntax in boot.ini from Alpha ARC BIOS or how closely ComDECpaqHP is with microsoft?
People who know what they're talking about
Oh, and while you're going to bash apple for running 68k code in emulation on PowerPC, At least Apple gave you something that worked, as slow as it was. I guess microsoft and intel never emulated anything, that wowexec program must just be for show. And all that microcode in the CPU, there's no emulation there!
Apple never tried to get out of the current trend of things or anything: MkLinux, Copeland, AIX, Rhapsody. They couldn't convince their user base to jump ship to a new platform or operating system without the applications already in place, and nobody wanted to write for Windows and MacOS as it was. Is it a problem yes, but hardly an apple specific one.
"Imagine using a machine that didn't have virtual memory and ran out of memory [if you didn't have enough]..." Imagine using a machine where nobody will ever need more than 640k, nobody will ever need more than 15 IRQs, nobody will ever need more than 3 DMA channels, nobody will ever need more than one MFM/RLL hard drive controller, nobody will ever need more than one VGA card, all cards will run at 8.3MHz for all eternity, all cards and BIOS's will be ISAPnP, all CPUs will be genuine Intel, there will always be enough conventional memory, and all drivers run in real mode and there will never be any conflicts.
Guess who was writing the "business" programs for Apple when they started out with Macintosh? Your good buddy microsoft [and Aldus/Adobe].
"But Windows caught up and overtook the Macintosh, both in terms of user interface and developer tools." Yeah, inventing your own closed, proprietary APIs at every turn and forcing everyone to use them didn't have anything to do with that. DirectX, ActiveX, COM/COM+/DCOM, SMB/CIFS, DirectDraw, Direct3D, DirectInput, Microsoft JVM, Internet Exploder, Exchange, NTFS, etc. All competeing with already existing standards, but rather than implement them, we'll make an incompatible, competing version of it, not tell anyone how it works, and cause more diversion to increase lock in while we're at it. You won't be a good microsoft zombie if you write code for anyone other than them or use something that actually follows a real standard rather than microsofts deliberately poor implementation of it.