28 May 2017, 19:55 | #1 |
Registered User
Join Date: May 2017
Location: Belfast
Posts: 750
|
Os3.9 uae to real 1200
Being never satisfied I decided that my current 2gb hdd in the amiga wasn't enough so pulled out an old 160gb ide drive and went about setting it up. Used winuae and a hard file of os3.9 to setup the drive which went fine then installed classic workbench 3.9, copied my files and thought that was me done.
But... when I put it in the amiga it boots then resets (presumably loading the scsi.device for pfs3) then just sits with the hdd light on constant. I've left it for ages, 10 minutes but nothing happens. I did notice even on winuae a pause when booting but surely it can't be that much. Any ideas why it won't boot in the real Amiga? It's a 3.5" drive so I'm using it connect to port 0 of my idefix board. |
28 May 2017, 21:24 | #2 |
Amithlon Fanatic
Join Date: Aug 2015
Location: Lexington, SC / US
Posts: 781
|
How did you partition it? A real Amiga needs the first partition of a larger HD to be less than 4 GB or it won't be able to read it. It then can boot and load a newer scsi.device off the HD than what is in ROM, and then access larger drives.
|
28 May 2017, 21:55 | #3 |
Registered User
Join Date: May 2017
Location: Belfast
Posts: 750
|
It's a 3.1 rom. The first partition is 2gb.
|
28 May 2017, 22:16 | #4 |
Amithlon Fanatic
Join Date: Aug 2015
Location: Lexington, SC / US
Posts: 781
|
Weird. I setup my HD on my Amiga 4000 like you did. It was a 160 GB I believe as well.
I did a 4 GB boot partition and left the rest for later and then installed OS 3.9 on it and patched it up. I made sure my WinUAE config was like my A4000, using the A600/A1200/A4000 IDE as the controller for the HD, not the UAE device. Moved it to the A4000 and then configured the rest of the partitions there. Worked great. |
28 May 2017, 22:30 | #5 |
Registered User
Join Date: May 2017
Location: Belfast
Posts: 750
|
Only difference I made to uae was to use an 040 at fast as possible speed so to make the installation and copying of files quicker. Don't think that would matter really as I did the same for my current 2gb drive.
I'll connect it back to the laptop and have another look. If need be I'll reformat the 2gb partition ffs. Just out of interest if I change the parameters of the first partition will it mess up the other partitions? |
28 May 2017, 22:43 | #6 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 6,987
|
160 GB requires LBA 48. LBA 48 support in OS 3.9 is broken. Be sure not to use more than the first 128 GB of the drive to avoid LBA 48.
In WinUAE you should select IDE controller so that you get the same problems there. Then you don't experience bad surprises on the real hardware. |
28 May 2017, 22:52 | #7 |
Amithlon Fanatic
Join Date: Aug 2015
Location: Lexington, SC / US
Posts: 781
|
Let me detail my process a little better than I did. I have a fully patched A4000 WinUAE setup that boots off a 4 GB CF card (which I can pull out and put in my A4000T which also boots off a 4 GB CF card). I added the IDE drive to that configuration and partitioned it out with the patched HDToolBox and patched scsi.device my WinUAE A4000 configuration has. I then started restarted WinUAE and setup a new A4000D config using only the IDE HD I had just partitioned (A600/A1200/A4000 IDE device 0) and a CDROM drive, (device 1). I then used the Emergency Boot .adf I had created for my primary WinUAE setup to install OS 3.9 on the 4 GB PFS3_AIO partition. When that was done I moved the drive over to my A4000D and it worked just fine.
|
29 May 2017, 10:50 | #8 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,507
|
Broken LBA48 = instant crash when anything outside of first 128G is accessed. (which PFS3 does because its "superblock" is located on the last block of partition)
For example http://aminet.net/package/driver/media/SCSI4345p has working LBA48 support. (LBA48 fix by me ) Anyway, as Thomas said, better emulate exact same hardware, including IDE controller to confirm working HD setup (make sure KS ROM is exactly same and emulated hardware is A1200), it is much easier to troubleshoot. If it still does not work on real hardware: it is practically always hardware level incompatibility but first set emulated IDE drive as "ATA2+ Strict", if you get identical crash/errors in emulation: maxtransfer value is wrong. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
New OS3.9 Classic wb install (CF) not booting on real amiga. | trydowave | support.Hardware | 53 | 27 April 2019 04:51 |
OS3.9 install works WinUAE but not with CF in real Amiga | eebuckeye | support.WinUAE | 26 | 12 May 2014 15:16 |
Real 1200 Slower vs WinUAE 1200 Same settings... | Pioneer500 | support.Hardware | 4 | 11 May 2013 15:43 |
Configure OS3.1 in WinUAE HDF and transfer to real HD | protek | support.WinUAE | 3 | 10 November 2009 15:32 |
ClassicWB OS3.9 problem on Real Amiga | Echelon | project.ClassicWB | 16 | 31 March 2009 22:17 |
|
|