#vd0: and 16 megs
9 messages in this thread
I realize that the limitation of 8 megs exists, but on my accelerator, which
has 16 megs, upon a reboot, when I remount vd0:, all that data is lost. I
assume it has to do with the configuring of memory beyond the 8 megs that are
autoconfigured.
I had the same problem here when I upgraded to a 3000.
A local BBS had a version which works fine on my 18meg system. Don't think
it's an ASDG approved patch, but with their approval I will upload it
here
Peter
— AutoPilot Engaged —
I tried this patched version and as long as I made a directory (such as vd0:t)
it worked fine. But as soon as I put any files in vd0:, it would loose
everything. I'm using WB2.1
Hi Michael,
To quote you:
> and as long as I made a directory (such as vd0:t) it worked fine. But
> as soon as I put any files in vd0:, it would loose everything.
I run a T directory in VD0: as well, but do also place files in the root
of VD0:, and haven't had any trouble in the 5 weeks I've had the 3000.
I'm also running 2.1, so I don't see where the difference comes in.
Peter
— AutoPilot Engaged —
How much memory do you have? The vector accelerator that I have is expanded to
16 megs.
Hi Michael,
> How much memory do you have?
A3000 with 2meg Chip and 16 meg Fast ram.
— AutoPilot Engaged —
Ok, the next question is that in WB 2.0 and 2.1, there is no driver for rad: in
the devs: directory. I assume that it is on the kickstart rom. Could you echo
the mountlist entry for rad:?
Hi Michael,
Here's my RAD: entry from the Mountlist.
RAD: Device = ramdrive.device
Unit = 0
Flags = 0
Surfaces = 2
BlocksPerTrack = 11
Reserved = 2
Interleave = 0
LowCyl = 0 ; HighCyl = 79
Buffers = 5
BufMemType = 1
BootPri = -129
Mount = 1
#
Good luck
Peter
— AutoPilot Engaged —
thanks. I'll try this tonight.