Hi,
When trying to get Chuckie Egg 2023 running from PiFS (discussed briefly here: viewtopic.php?p=441464#p441464),
I came across an issue where PiTubeDirect would lock up.
Basically, when trying to run an older version of the game, the computer would lock up during initialisation of the game, but then on BREAK / CTRL-BREAK, the computer would hang just after printing the BASIC message, and to recover, I would either have to power cycle the beeb, or reset the beeb into the IntegraB IBOS 'No Language Environment' (NLE) and use the *FX151,230,x to change Co-Pro type.
The NLE is invoked very early in the boot sequence, and disables the Co-Pro, before dropping you to the * prompt. So, for example, I would change to Co-Pro 0 (from the default 24), and then if I hit BREAK / CTRL-BREAK it would reset properly, print the BASIC message, and drop me back to the BASIC command prompt. I could then switch back to the default Co-Pro 24 and that would work again. When at the NLE * prompt, I tried *FX200,3 to see if that alone would trigger a successful reset, but it didn't. I still needed to switch to a different Co-Pro before it would recover.
The conditions to make it lock up do seem to be quite specific (ie, a specific version of Chuckie Egg 2023, running from PiFS, and running on real hardware), so I'm not sure how easy it will be for others to replicate, but I'm happy to provide more details and do any further testing required using my specific hardware.
Ultimately, I was able to get the game running by installing from the latest Chuckie Egg disc image to my PiFS, but it seemed odd that any code should be able to lock up PiTubeDirect in the way it did!
When trying to get Chuckie Egg 2023 running from PiFS (discussed briefly here: viewtopic.php?p=441464#p441464),
I came across an issue where PiTubeDirect would lock up.
Basically, when trying to run an older version of the game, the computer would lock up during initialisation of the game, but then on BREAK / CTRL-BREAK, the computer would hang just after printing the BASIC message, and to recover, I would either have to power cycle the beeb, or reset the beeb into the IntegraB IBOS 'No Language Environment' (NLE) and use the *FX151,230,x to change Co-Pro type.
The NLE is invoked very early in the boot sequence, and disables the Co-Pro, before dropping you to the * prompt. So, for example, I would change to Co-Pro 0 (from the default 24), and then if I hit BREAK / CTRL-BREAK it would reset properly, print the BASIC message, and drop me back to the BASIC command prompt. I could then switch back to the default Co-Pro 24 and that would work again. When at the NLE * prompt, I tried *FX200,3 to see if that alone would trigger a successful reset, but it didn't. I still needed to switch to a different Co-Pro before it would recover.
The conditions to make it lock up do seem to be quite specific (ie, a specific version of Chuckie Egg 2023, running from PiFS, and running on real hardware), so I'm not sure how easy it will be for others to replicate, but I'm happy to provide more details and do any further testing required using my specific hardware.
Ultimately, I was able to get the game running by installing from the latest Chuckie Egg disc image to my PiFS, but it seemed odd that any code should be able to lock up PiTubeDirect in the way it did!
Statistics: Posted by KenLowe — Tue Dec 10, 2024 5:37 pm