Kick.38n.20 and GVP
5 messages in this thread
Has anyone else out there had trouble getting kick.38n.20 (the one released
at the DevCon…) running with a GVP Impact hard disk controller? (NOT the
030' card, mind you…) The older kickfile (32e) works just fine, but the
new one causes a system error as soon as Binddrivers is executed under the
2.0 environment. (ie, just when it is loading in the scsi driver and
mounting the hard disk…)
A educated guess is that perhaps the GVP is trying to load the FFS from
the hard disk boot area (I *know* it gets the mount info from that area…)
and that the version of FFS there is no longer compatible with the released
kickfile. Or maybe their scsi driver itself isn't liked by the new
kickfile.
Anyone else having a problem with this? Or similar problems?
–>Steve Bennett
Have you tried calling GVP? Also, did you read the 'readme' files on the
Kickstart disk? I read through them and was confounded at the complexity
of trying to make a dual-boot system… I have a GVP '030 on loan, plus a
separate Impact controller with 2 megs and autoboot, so I'm in the same
boat you are. I haven't tried it yet. You do need to reformat the WB 2.0
boot partition, right? The readme said something about that, buried in the
details. (Also note that it still calls it 1.4, not 2.0. 🙂 I think
there's differences in WB 2.0 FFS, as compared to WB 1.3. Maybe it's
backwards compatible on non-boot partitions.
Did I miss something, or are there easier ways to get 2.0 up and
autobooting on the A2000?
I got mine setup by just copying the 2.0 Workbench and Extras disks to my
non-primary partition, already set up ffs. I put the Kick.38n.20 file on my
DH0: partition and created a script file to execute Kickit (which I copied
to DH0:c from the Kickfile disk.). I created an icon that called XICON
whihc also executes the same script file.
I use SetCPU to turn off some of the stuff I use (CARDROM, CACHE, etc.)
then call kickit. After you get the warning to enter CTRL-C within 6
seconds, hold both mouse buttons down. Up will come (after the screen
flickers)a screen listing all partitions. I just click on my DH1: partition
to make it boot there. 2.0 then comes up just fine.
This is independent of the GVP 68030 specifics that requires a special
kickfile and new PALs on the GVP.
Hope this helps.
-Greg
The methos I described is the only way to have dual operating systems on a
2000. The 3000 has 2.0beta3 Roms that support the dual boot feature. -Greg
Actually, I'm NOT using the 030 system, and I'm working off of a boot
floppy and I've had it working before under an earlier beta 2.0. It's just
with this particular kickfile version that I've started having trouble.
I may indeed need to reformat my disk. I hope not. It was quite a
surprise to me, mind you, that the GVP driver knew enough to mount my hard
disk when the driver was loaded, even though it WASN'T listed in the
mountfile on the floppy. I think this is why I'm having trouble in the
first place.
Oh well, I'll try calling GVP. (Not that I've had much luck with calls
to them before… <sigh>)
–>Steve Bennett