VD0: and accelerator
9 messages in this thread
How do you have them setup. I also recently got a Vector accelerator and
have had no problem with VD0: Perhaps you could post the part of your
startup-sequence where you mount them…. Mike
I just got a version off of the board that has been modified to work with a
3000. I installed in on the HD and got it to work fine. Originally it
would come up and say 'NOT A DOS DISK' but it could be because the previous
vd0: driver was active. RAD: was also acting flacky, where it would be
okay when mounted but on reboot it was not mounted until I gave the mount
command. The startup-sequence is exactly 2.1, where any additional
commands I put in the user-startup. Anyway, this morning, I booted up in
the 68000 mode, mounted vd0:, rad: and when I rebooted in the 68030 mode,
everything was fine. On another subject with the vector, I received mine
with a true 68030. I was wondering what the advantages are since the
vector already maps kickstart into 32 bit memory regardless of a MMU. exot
If you have an AMAX II Mac emulator, it will make use of the MMU. Other
than that, I can't think of much. Oh, C='s Enforcer program will use the
MMU to trap certain errors. Mainly of use to programmers, I gather.
Well, the use of rad: and vd0: still are not working. VD0: keeps loosing
past files on reboot. Sometimes rad: works. I did download the virtual
drive demo that uses the MMU to use the hard drive as memory. I geuss that
I will talk to IVS monday.
Does anyone get VD0: to return memory when files are deleted from it?
On my A3000 w/2.04 memory is returned immediately from VD0:
How many bites is your VD0: thingie?
vdisk.device 2724
Then we are using the same version of ASDG-RAM. I tried a few different
things last night, one where I disabled the 32bit mem via Vectors startup
and both RAD and VD0 worked. I have 16 megs on the Vector board. Maybe
there is a problem with RAD and VD0 concerning memory beyond 8 megs.