jimb@amdcad.UUCP (Jim Budler) (04/01/86)
I posted ramstart 1.21 to the net a while ago, and stated that it could be used, but not autobooted on a Mac+. I made the same statement on Compuserve and received the following in reply: Fm: Gary Boudreaux 76344,2426 To: Jim Budler 72415,1200 Jim (and All): Here are the changes to make RamStart compatible with HFS. These changes are confirmed on version 1.22, and I'm fairly confident that the patches will be the same for version 1.21. Use Fedit as follows: [It turns out there WAS a difference between 1.21 and 1.22. After several interchanges came the following:] Fm: Gary Boudreaux 76344,2426 To: Gerald Edgar 70715,1324 (X) OK. I broke down and downloaded RamStart 1.21, and here are the applicable patches: In sector $0C, offset $B4, replace 4EBA 0682 with 4E71 4E71 In sector $0D, offset $17A, replace 6700 0012 006E 8000 with 6000 0012 006E 8000 If you're using a hard disk, you may need to apply the following patch (I had to use it for both the Corvus and the Warp Nine): In sector $06, offset $190, replace 41FA 0388 with 6000 000C The symptom for this last problem is a message "can't find our drive #". I'm not sure why you got this message even with floppies, but I consider it safe to go ahead and apply this last patch anyway. Another note (for those who didn't see the 1.22 patches): RamStart uses a DRVR 10, which is a problem if you're using AppleTalk. To get around this, pick a driver number which isn't being used in your system file, and use ResEdit to change the DRVR number in RamStart (I used 11 on my system). -- Jim Budler Advanced Micro Devices, Inc. (408) 749-5806 Usenet: {ucbvax,decwrl,ihnp4,allegra,intelca}!amdcad!jimb Compuserve: 72415,1200