AMax Prob. Continued?
3 messages in this thread
Dan –
Have you heard from ReadySoft or GVP on a fix? I'm still twisting in the
breeze here…
Also, how were you able to boot into 68000 mode? I tried it and see to
have continually ended up in 69030 mode – as noted by SetCPU.
Thanks – Joe
Joe: I haven't heard anything (haven't called them, either) – Raymond said he
wd he would notify both of us when he had a solution.
On booting for the 68000 – you'll need to have a bootable disk ready with the
appropriate stuff in Devs etc. for mounting the harddrive.
Use GVPCpuCtrl – clicking it from Workbench should send your machine into a
reboot (from DF0) in 68000 mode. Or, use the CLI and enter "GVPCpuCtrl
BOOT68000" – this is for A500s and A2000s only.
YOu should get a request for bootable workbench disk if one isn't in DF0>
I'm not really using the AMAX as yet – I want to know that the GVP problem has
been resolved before committing any work to it.
Let me know if you hear anything or find a new solution (or problem) –
Dan
Joe,
Our Amiga 2000HD has a GVP G-Force 030 accelerator board. On a
diskette that came with the board, there is a GvpCpuCtrl program which,
among other things, will boot the system into 68000 mode. The G-Force 030
board is completely disabled. That includes the 68030, 68882, onboard
32-bit RAM, and the SCSI port.
Since booting into 68000 mode is GvpCpuCtrl's default, just clicking on
its icon will start the reboot. I used it once when the onboard RAM
conflicted with the bridgeboard. After I removed the J12 jumper to make
the 32-bit RAM extended, there was no longer any conflict. I am quite
pleased with the GVP G-Force 030 accelerator board.
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless' from the Rocket City!
via AutoPilot 1.03a