(Part 3 of 3..Due to Size) Ivan Drucker provided photos of his disassembled 2400 to mac2400 back in the early years. The attached reflects his latest exploits in getting OSX to run on the 2400...a 603e at that.
I'll try and get this on mac2400 over the weekend, and Ivan has even suggested he might do a step-by-step, but in the meantime he agreed that I could post this to the DuoList. He isn't currently a subscriber....but we're working on it. ;-) Continued from Part 2..... > >it, and, sure enough, it booted. And the CompUSA Ethernet card worked too! > >But I wasn't out of the woods yet -- what about FireWire? I downloaded >the FireWire extensions for 8.6 from Apple (2.4 is the last version >supported for that OS). They didn't do anything, which surprised me since >the OWC site showed the card as working from 8.6 onward. A little >research led me to discover that while Apple provided the interface >support, they did not include driver support for third-party storage >devices until FireWire 2.7, which surfaced in Mac OS 9.1. (Later, I >noticed my OWC receipt, unlike their website, says the card works on 9.1 >and up.) For earlier versions of the FireWire extensions, you have to use >a third-party driver with an external drive. I didn't really WANT to >install a third-party hard drive driver -- I like to keep things simple >-- so I instead I thought I'd try the FireWire 2.8.3 extensions from Mac >OS 9.2.2 when someone on the net reported that they still work on older >systems. I had to actually extract them from the Tome in the 9.2.2 >updater, because the FireWire PC Card Enabler extension wasn't installed >on my iBook! And that did it. Put in the card, up came the disk. Nice. > >So now I had it all! Phase I: I got X installed. Phase II: I got >networking working with. Phase III: I got FireWire storage working with >it. And as a bonus, my 2400 is now Cardbus-enabled, and it all works in >8/9 as well. > >If anyone wants to give this a shot, one key tip I have (especially since >I can't reinstall without removing the drive) is to use Apple Software >Restore with Disk Copy to make images of your X volume as you go along. >For this reason, I suggest you keep your X partition under 2,047 MB (the >max size imageable by Disk Copy 6.3.3). The technique is to image the >volume with Disk Copy, and then if you wish to restore it, you first >mount it with Disk Copy, and then launch ASR and drag the mounted image >into it. Choose your X partition as your target, and tell it to wipe >everything. If your X volume is over 2,047 MB, you can use ASR alone for >creating your image, though I haven't done this. For more on this >technique, check out http://www.bombich.com, which is where I learned >about it. > >If you run Norton Speed Disk (6.0 or later only!) with the Speed Disk 3.2 >profile before imaging, it will help keep the image smaller because all >the blank space at the end of the disk won't be saved as data in the >image. Also, running Disk Warrior and/or Disk Doctor before Speed Disk is >a good idea too. > >It's great to be running OS X on my 2400, and it's amazing that as much >work as it does. However, it obviously wasn't designed for the machine, >and certain things simply don't work. Ryan Rempel, the author of >XPostFacto, is working hard to try to support everything, but there will >probably always be some things that won't quite go. Here are some issues: > >- Speed. Without my much-missed G3 card, OS X is just too slow to use for >anything but a server or for a Terminal window. There's no other way to >say it. It's not so slow that you can't do anything, but it's definitely >no fun. People say that Jaguar is faster, so maybe that will help things, >but I still think the graphic demands are just more than the 603 will be >able to handle. Some notable performance improvements can be had by >running ShadowKiller and Tinkertool, and in the latter disabling font >smoothing and the Desktop. But it's still slow. > >- Memory. I'm fortunate enough to have 112 MB in my 2400, but it's no >secret that OS X likes memory and that you're not going to want to run >many applications at once lest you go into spasms of VM swapping. I >imagine it would only be worse on the typical 80MB machine. Fortunately, >Terminal is mostly what I've run. > >- Sleep. It doesn't work at all, and can even cause bad things to happen. >Therefore one of the first things to do after installing XPF is to tell >Energy Saver to never sleep. The author is apparently working to fix this >issue. > >- Classic. The memory limitation precludes running Classic, so I simply >don't. Even if I did have the memory, a common XPF issue is that Classic >wants 9.2.x and the machine doesn't support it. There are various >solutions for this. One is that that supposedly 9.1 will still work in >Classic (though I am sure 8.6 doesn't). Another is that there are hacks >(which look pretty ugly) to make 9.2.1 run on older machines. Still >another is to install 9.2.x into Classic -- but it will only boot there, >of course. > >- Sound is at max and is unadjustable. This is a general XPF issue on all >machines. I deal with it by just sticking a cable into the headphone jack. > >- Backlight is at max and is unadjustable. I discovered that if I want to >run in "server mode" that I can turn off the backlight by typing >something into Open Firmware, and then I can "boot blind." You can still >sort of see the screen if you shine a light on it. I can't remember the >command off the top of my head but I'm sure I can figure it out >again...simply typing " backlight-off" (that's a space after the first >quote) might work, actually. Then you have to type "boot" to get things >going. > >- Color Calibration. The 2400 screen is really pretty bad by default; >everything is pale blue and washed out. You can't even see the stripes in >the menu bar. It's key to run the ColorSync calibrator to get things >looking ok. Even after that, you'll realize the color range limitations >of the 2400 compared to later LCD's... > >- Starting up with both PC cards in at the same time causes neither to be >recognized, even if manually ejected and reinserted. Starting up with one >and then inserting the other seems to work ok. I assume this is an XPF >issue though in theory it could be an OS X issue...only a Wall Street >owner would know. > >- Changing the slot for the Ethernet card (from upper to lower, for >example) confuses the system and registers the card as a new interface. > >- Ejecting the Ethernet card while it is in use (or not in use) will >cause a kernel panic. This might be a 10.1.5 issue, based on a KB article >I read. > >- It seems that no 16-bit PC card is recognized, even the simplest >modem-only cards or ATA cards (hard drives, Compact Flash, etc.) which >would certainly work with OS X on a supported machine. This appears to be >an XPF problem. > >I'll send some snaps along later if I can make my cheapo digicam do what >I want. > >Cheers, >Ivan Drucker >[EMAIL PROTECTED] New York Ralph Mawyer, Jr. San Antonio, Texas Associate Editor mac2400 ... http://www.sineware.com/mac2400 Your PowerBook 2400 Reference Site "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin, 1759. ---------- Duo/2400 List, The friendliest place on the Net! A listserv for users and fans of Mac subportables. FAQ at <http://www.themacintoshguy.com/lists/DuoListFAQ.shtml> Be sure to visit Mac2400! <http://www.sineware.com/mac2400> To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> Need help from a real person? Try. <[EMAIL PROTECTED]> ---------- Dr. Bott | 10/100 Ethernet for your 2400 is finally here! MPC-100 | <http://www.drbott.com/prod/mpc100.html> RoadTools $30 PodiumPad available at Apple retail stores, $20 Traveler CoolPad at Staples. Both in white for iBooks at <http://roadtools.com> Midwest Mac Parts ][ <http://www.midwestmac.com> After-market parts for Macs. ][ 888-356-1104 ][ MacResQ Specials: LaCie SCSI CDR From $99! PowerBook 3400/200 Only $879! Norton AntiVirus 6 Only $19! We Stock PARTS! <http://www.macresq.com>
