Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: AndyFC on November 17, 2012, 07:52:12 PM
-
I've finally managed to unite my A1200 and the ClassicWB build which I built in WinUAE (thanks to everyone for their help in response to my thread about how to clone the virtual disk onto my real amiga HD).
On the real Amiga, I've added the line c:mumove4k PREPAREEMUL to the s:startup-sequence, just before the setpatch.
The Amiga begins to boot, and then reboots (it didn't do this before I added the line so it is doing something), but then I get a red screen. This happens every time.
Any idea what the cause is, and how to fix please?
hw is A1200, blizz 1230 mk IV, with 32 MB RAM. At this point, nothing else added in.
Thanks.
-
Don't the docs to MuMuove4k give some special warnings about the PREPAREEMUL parameter?
-
I've finally managed to unite my A1200 and the ClassicWB build which I built in WinUAE (thanks to everyone for their help in response to my thread about how to clone the virtual disk onto my real amiga HD).
On the real Amiga, I've added the line c:mumove4k PREPAREEMUL to the s:startup-sequence, just before the setpatch.
The Amiga begins to boot, and then reboots (it didn't do this before I added the line so it is doing something), but then I get a red screen. This happens every time.
Any idea what the cause is, and how to fix please?
hw is A1200, blizz 1230 mk IV, with 32 MB RAM. At this point, nothing else added in.
Thanks.
I seem to recall having the same issue.
I think you need to specify an additional param, or maybe I never did get it to work.
I just checked my system, and I'm using a blizkick module...
You might consider doing that...
http://aminet.net/package/util/boot/BlizKick
C:BlizKick QUIET DEVS:NATEX.ROM EXTRESBUF=30000 MODULE A1000Jingle BBlank DosResetCard PrepareEmul MuMove4K MoveVBR Libs:mathieeesingbas.library Libs:mathffp.library DEVS:scsi.device
this is my blizkick line, i think you replace natex.rom with * to use the actual ROiM.
blizkick is much better because you can consolidate all those reboots into one. Its better for other reasons too.
-
Try:
c:MuMove4k PREPAREEMUL A1200
-
Adding the A1200 parameter worked. Thank you.
Almost everything is up and running now - I had to reduce the maxtransfer rate on the HD, as some large files were corrupting (roms for Shapeshifter or whdload mainly) and I've set up the CD ROM, so I can transfer files from a PC when needed. I just need to fix a broken wire in my mouse too - the pointer doesn't move sideways).