OS 3.9 Emergency boot disk

[WarPiper]

Hi can some one please let me know where I can get instructions on installing a OS 3.9 on winuae,  I have made a rom image of my 4000, made a emergency boot disk, have OS 3.9 cdrom, though its a copy (my original cracked when my son jumped on it, the couch was a bad place to put it).  

I have followed the instructions on this page http://home.t-online.de/home/thomas-rapp/os39uae.html but it tries to make me boot from the cd rom with no emergency boot disk image, I just get to a cli prompt, no commands work because none are installed, so I try to boot off of my EMERGENCY BOOT IMAGE and I get a cache cdfs error, can not open "asim_atapi.device" unit 1, and then another requester asking me to insert AmigaOS3.9 in any drive.

can some one please help. thanks

[Thomas]

I have followed the instructions on this page http://home.t-online.de/home/thomas-rapp/os39uae.html but it tries to make me boot from the cd rom with no emergency boot disk image, I just get to a cli prompt, no commands work because none are installed

Make sure you have the s/startup-sequence file in the right place. If you add directory C:\WinUAE\Workbench to WinUAE's hdd list, there must be C:\WinUAE\Workbench\s\startup-sequence as described on the page. Also make sure that startup-sequence has no extension (e.g. .txt). There is an option in Windows Explorer to hide known extensions. Disable this option to see and remove the extension. Or use the DOS command Rename.

so I try to boot off of my EMERGENCY BOOT IMAGE and I get a cache cdfs error, can not open "asim_atapi.device" unit 1, and then another requester asking me to insert AmigaOS3.9 in any drive.

Either change the EMERGENCY_CD file on your emergency disk to call uaescsi.device unit 0 instead of asim_atapi.device unit 1 or add your CD-ROM to WinUAE as a harddisk directory called AmigaOS3.9. The latter method might give you some problems (all files names in upper case, write protected files etc.)

Please ask again if you need further support.

Bye,
Thomas

[WarPiper]

thanks will try it now

[WarPiper]

ok, I deleted the .txt fron the startup-sequence file, then created a emergency boot disk, the exited winuae and deleted the cdrom directory then added the emergency disk on floppy page to df0: then I click ok, the winuae starts to load the disk and then I get alot of AMIGAOS3.9 has read errors, then the desktop appears with no icons and no menu, just a backround, I cant even get into a shell

[KennyR]

winuae starts to load the disk and then I get alot of AMIGAOS3.9 has read errors, then the desktop appears with no icons and no menu, just a backround, I cant even get into a shell

The same happened to me when I tried to install OS3.9 a while back on UAE. UAE is broken. Instead of setting up your CDROM as a device on its own, select Mount PC Drives and use the CDROM that way. Not quite as flexible but at least the disc will be readable.

[WarPiper]

where and how do I do that, I dont see a provision for that, I am using winuae 0.8.22 r6

[WarPiper]

I clicked ok add pc drives at startup but does that mean that I should not delete the cdrom  drive from the directory?

[Mad-Matt]

KennyR wrote:
UAE is broken. Instead of setting up your CDROM as a device on its own, select Mount PC Drives and use the CDROM that way. Not quite as flexible but at least the disc will be readable.

The solution is easy and os35/39 installs perfectly fine from the emergancy boot floppy Image.

on the boot floppy just knock off a few Fs from the Maxtransfer line in the CD0/CD1 Mount file.  It will install just fine.

I can send working Boot Images if anyone needs them. Come into #Amihelp sometime on arcnet and see if im around and ill dcc.

Matt
------

[KennyR]

If you activate Add PC Drives you must remove the CDROM entry from the list, or UAE will get confused. Or rather, AmigaOS will.

[Thomas]

It does not make any difference if you check "Add PC drives at startup" or not, because WinUAE no longer includes CD-ROM drives with this option. CD-ROM drives must either be added explicitly or by uaescsi.device emulation.

I get alot of AMIGAOS3.9 has read errors

As told before this is a MaxTransfer issue. A restriction of ASPI as Toni Wilen said.

Boot again with this startup-sequence thing and without the emergency disk in DF0. Then insert the emergency disk. Open a Shell window (in Emergency-Boot/System) and enter ed df0:devs/emergency_cd (I hope the editor works on this extemporized environment).

Now search the line that reads MaxTransfer = 0xffffffff and change it to MaxTransfer = 0xfc00

Then press Esc and enter X to save the changes. Enter Q instead of X to discard the changes.

Bye,
Thomas