12 March 2017, 18:42 | #1 |
Registered User
Join Date: Mar 2010
Location: uk
Posts: 214
|
ClassicWB ADVSP and OS39
Hi all
Anyone have a Pink screen with ClassicWB OS39 it will NOT boot-up with my real A1200 ???? Now set-up ClassicWB ADVSP this boot fine BUT only show DH0,DH1,DH2 drive and the forth DH3 show DH3:NDOS this is a 16GB CF card, if I put card in my PC and load WinUae this work fine any ideas . . . |
12 March 2017, 19:37 | #2 |
Registered User
Join Date: Oct 2012
Location: South Shields
Posts: 812
|
Do you have 3.1 roms in your real A1200? 3.9 will not work at all without them (I think you can use Blitzkick or RemApollo to soft kick them first if you don't).
Second problem looks like you are using the standard scsi.device and need to use an updated one to access the entrie drive using loadmodule command. |
12 March 2017, 20:22 | #3 |
Registered User
Join Date: Mar 2010
Location: uk
Posts: 214
|
Yes 3.1 form amigakit
|
12 March 2017, 22:16 | #4 |
Registered User
Join Date: Mar 2010
Location: uk
Posts: 214
|
The version scsi.device 40.12 old, I look in DEVs and there is no scsi.device?
So how do I update to 43.45 is there a install for ClassicWB ADVSP??? Last edited by iowtheme; 12 March 2017 at 22:34. |
12 March 2017, 23:09 | #5 |
Banned
Join Date: Dec 2016
Location: Nottingham, UK
Posts: 481
|
The "easy" way is to use a 3.z ROM.
The "difficult" way is to cook your own ROM with a different set of devices. The "middle" way is to add a line or 2 to your startup-sequence to use an upgraded .device or .library. Big ass thread on it here, Thomas Richter was very patient with noob me on this... http://www.amiga.org/forums/showthre...t=Loadresident The "middle" way means your boot disk still has to be under 2Gb and use Fast File System, but at least other partitions can be bigger. Last edited by Pat the Cat; 12 March 2017 at 23:14. |
13 March 2017, 01:51 | #6 | |
Registered User
Join Date: Oct 2012
Location: South Shields
Posts: 812
|
Quote:
To do this you need to add the command loadmodule to your C: dir and a newer scsi.device in Devs: - the filename is not important as you can specify anything you want to when you type the command into the startup-sequence. You can get loadmodule from aminet or from a classicwb archive, same goes for the scsi.device. Loadmodule is in MyFiles/LargeHD/Tools/ and you can pick a scsi.device from MyFiles/LargeHD/128GBSupport/ I would suggest using version 43.45. Put the files in the correct places then add this line at the top of your startup-sequence C:Loadmodule Devs:A1200.scsi.device.43.45 (or whichever one you are going to use). If using 3.9 you also need to add the option "skipromupdates" to setpatch I think, so add it onto the end of that line in the ss. |
|
13 March 2017, 14:46 | #7 |
Banned
Join Date: Dec 2016
Location: Nottingham, UK
Posts: 481
|
Filesystem TYPE is stored in RDB.
The actual filesystem of the boot partition has to be available (stored in ROM) for the system to be able to access the boot partition and start up from it. |
13 March 2017, 19:43 | #8 |
Amigan
Join Date: Feb 2012
Location: London
Posts: 1,321
|
That's incorrect. The FS is stored in the RDB too. That's why you can boot from a PFS disk.
|
13 March 2017, 20:44 | #9 |
Registered User
Join Date: Oct 2012
Location: South Shields
Posts: 812
|
I've seen a few comments on forums from other people about your replies to questions/posts being utter rubbish, and this is another example of it.
|
13 March 2017, 20:46 | #10 |
Banned
Join Date: Dec 2016
Location: Nottingham, UK
Posts: 481
|
Checked, the filesystem isn't stored in the RDB, but a pointer to a filesystem can be stored in an RDB.
https://en.wikipedia.org/wiki/Amiga_rigid_disk_block http://wiki.amigaos.net/wiki/RDB So you can boot off a PFS3 or other filesystem disk, up to the point where the filesystem isn't available (SYS:L directory is corrupted). On the other hand, if you do use FFS for your boot partition file system, if will be accessible even if the SYS:L directory is corrupted... so I know what I prefer for my boot partition, thanks. Last edited by Pat the Cat; 13 March 2017 at 20:51. |
13 March 2017, 21:21 | #11 |
Amigan
Join Date: Feb 2012
Location: London
Posts: 1,321
|
|
14 March 2017, 01:36 | #12 |
Registered User
Join Date: Mar 2008
Location: Manchester!
Posts: 308
|
With 3.9 I think i have to use skipromupdates scsi.device on my real amiga otherwise it doesnt boot..
Then I just use loadmodule and load an updated scsi device and it all works fine. I'll check tomorrow what my startup-sequence says. |
15 March 2017, 23:09 | #13 |
Registered User
Join Date: Mar 2010
Location: uk
Posts: 214
|
OK gays
this did not solve my problem so now partition it to three drive this work fine thank All |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Amidock from 3.9 to classicWB ADVSP | spannernick | project.ClassicWB | 3 | 26 May 2021 12:42 |
ClassicWB OS39 v2.5 update to v2.7 | amigappc | project.ClassicWB | 3 | 01 June 2013 21:04 |
To use OS39 or ADVSP (3.1)? | amigappc | project.ClassicWB | 11 | 31 December 2010 09:23 |
VGA Screen on ClassicWB OS39 | amigappc | project.ClassicWB | 2 | 27 December 2010 15:06 |
ClassicWB for OS39 | Bloodwych | project.ClassicWB | 134 | 17 May 2009 00:47 |
|
|