You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a ProDOS 2.4 image that I've installed GSOS 6.01 on, and it boots into Bitsy.bye normally (I modified the startup to this instead of GSOS/ProDOS). The ProDOS file is renamed to GSOS.
This works fine on my old CF card controller, and on emulators. It boots into Bitsy.Boot and I can choose to boot GSOS or BASIC, or whatever. However, on the Dan][, it gets an error $002F when you try to boot GSOS.
The weird thing is, if you have a floppy with GSOS in the 3.5 drive, it will boot when you choose the GSOS file on the hard drive. So, it seems something is pointing the system at the floppy drive instead of the Dan][ partition?
Card is in slot 7.
The games hard drive image assembled by Vince Briel (usually this is called Apple II Games (DOSMASTER)) has a similar problem when booting. It boots for a little bit then gets a Check Disk in Drive error.
The text was updated successfully, but these errors were encountered:
I have a weird issue I've noticed with the Dan][.
I have a ProDOS 2.4 image that I've installed GSOS 6.01 on, and it boots into Bitsy.bye normally (I modified the startup to this instead of GSOS/ProDOS). The ProDOS file is renamed to GSOS.
This works fine on my old CF card controller, and on emulators. It boots into Bitsy.Boot and I can choose to boot GSOS or BASIC, or whatever. However, on the Dan][, it gets an error $002F when you try to boot GSOS.
The weird thing is, if you have a floppy with GSOS in the 3.5 drive, it will boot when you choose the GSOS file on the hard drive. So, it seems something is pointing the system at the floppy drive instead of the Dan][ partition?
Card is in slot 7.
The games hard drive image assembled by Vince Briel (usually this is called Apple II Games (DOSMASTER)) has a similar problem when booting. It boots for a little bit then gets a Check Disk in Drive error.
The text was updated successfully, but these errors were encountered: