Ok, so there are quite a few things going on in this thread!
Firstly, there isn't a 'NODIR' command in IBOS.
Secondly, regarding NOBOOT, I'm not entirely sure what happens if you don't have a HDD installed, and you don't have an ADFS disc installed in your floppy drive (I understand you have a 177x based controller, so you should be able to read ADFS floppies). I suspect the ADFS still tries to read some information from the floppy disc even if NOBOOT is set. And, if there isn't an ADFS formatted disc in the drive, the beeb will possibly hang for a period before coming back with an error (It's about 1 min on the Master, IIRC). Unfortunately, I'm not in front of a beeb just now, so I'm not able to test that. BeebEm reports Disc Error 50 almost immediately, but I'm not sure how accurate that is.
I must admit, I'm a bit confused as to why you are using v1.33 of ADFS if you don't already have a CF / IDE based HDD. Unless you really need to use v1.33 for CF / IDE based HDDs, I'd be inclined to use the stock v1.30 for SCSI based HDDs. This is what you need to use if running BeebSCSI (either the original Simon Inns board, or the Pi1MHz implementation). FYI, the various ADFS versions are detailed here:
https://mdfs.net/System/ROMs/Filing/Disk/Acorn/ADFS.txt
Thirdly, regarding the use of 32k ROMs, these will not work reliably in a standard beeb without a wiring modification. So if you are trying to install this ROM in one of the beeb sockets, then this is likely to cause an issue. To avoid issues you can make a fairly simple wiring modification so the beeb will always read either the upper or lower 16k of the 32k ROM.
You can also make a slightly more complex wiring modification so the beeb can read both the upper and lower 16k of the ROM as separate banks. However, this modification should not be done if you have an IntegraB board installed (as you have). Instead of trying to make any wiring modifications to the beeb, you can install 32k ROMs into one of the 3 spare upper row of sockets on the IntegraB board, and set the jumpers appropriately. If doing this, make sure nothing is plugged into the ROM socket immediately below.
Firstly, there isn't a 'NODIR' command in IBOS.
Secondly, regarding NOBOOT, I'm not entirely sure what happens if you don't have a HDD installed, and you don't have an ADFS disc installed in your floppy drive (I understand you have a 177x based controller, so you should be able to read ADFS floppies). I suspect the ADFS still tries to read some information from the floppy disc even if NOBOOT is set. And, if there isn't an ADFS formatted disc in the drive, the beeb will possibly hang for a period before coming back with an error (It's about 1 min on the Master, IIRC). Unfortunately, I'm not in front of a beeb just now, so I'm not able to test that. BeebEm reports Disc Error 50 almost immediately, but I'm not sure how accurate that is.
I must admit, I'm a bit confused as to why you are using v1.33 of ADFS if you don't already have a CF / IDE based HDD. Unless you really need to use v1.33 for CF / IDE based HDDs, I'd be inclined to use the stock v1.30 for SCSI based HDDs. This is what you need to use if running BeebSCSI (either the original Simon Inns board, or the Pi1MHz implementation). FYI, the various ADFS versions are detailed here:
https://mdfs.net/System/ROMs/Filing/Disk/Acorn/ADFS.txt
Thirdly, regarding the use of 32k ROMs, these will not work reliably in a standard beeb without a wiring modification. So if you are trying to install this ROM in one of the beeb sockets, then this is likely to cause an issue. To avoid issues you can make a fairly simple wiring modification so the beeb will always read either the upper or lower 16k of the 32k ROM.
You can also make a slightly more complex wiring modification so the beeb can read both the upper and lower 16k of the ROM as separate banks. However, this modification should not be done if you have an IntegraB board installed (as you have). Instead of trying to make any wiring modifications to the beeb, you can install 32k ROMs into one of the 3 spare upper row of sockets on the IntegraB board, and set the jumpers appropriately. If doing this, make sure nothing is plugged into the ROM socket immediately below.
Statistics: Posted by KenLowe — Sun Jul 07, 2024 12:18 am