Ramworks Ramdrive [message #375220] |
Wed, 31 October 2018 20:14 |
|
Originally posted by: Anthony Adverse
Hey there and todays weirdo question is...
How to reconnect a RAMdrive after some bonzo piece of software has disabled it. I'm using the AE software that allows you to allocate everything over 64k to the ramdrive. But the volume keeps disappearing in certain applications. Just wonder if theres a way to make sure its active before running, say... copy II+
A
|
|
|
Re: Ramworks Ramdrive [message #375221 is a reply to message #375220] |
Wed, 31 October 2018 21:18 |
mdj
Messages: 301 Registered: December 2012
Karma: 0
|
Senior Member |
|
|
On Thursday, 1 November 2018 10:14:46 UTC+10, Anthony Adverse wrote:
> Hey there and todays weirdo question is...
>
> How to reconnect a RAMdrive after some bonzo piece of software has disabled it. I'm using the AE software that allows you to allocate everything over 64k to the ramdrive. But the volume keeps disappearing in certain applications. Just wonder if theres a way to make sure its active before running, say... copy II+
I suggest you leave the standard /RAM driver in place and install the AE driver in a different slot/drive location. That way, 128k software will only disconnect the standard /RAM driver, and correctly reconnect it when its done using the Auxilary bank.
|
|
|
Re: Ramworks Ramdrive [message #375223 is a reply to message #375221] |
Wed, 31 October 2018 21:24 |
|
Originally posted by: Anthony Adverse
On Thursday, November 1, 2018 at 12:18:03 PM UTC+11, mdj wrote:
> On Thursday, 1 November 2018 10:14:46 UTC+10, Anthony Adverse wrote:
>> Hey there and todays weirdo question is...
>>
>> How to reconnect a RAMdrive after some bonzo piece of software has disabled it. I'm using the AE software that allows you to allocate everything over 64k to the ramdrive. But the volume keeps disappearing in certain applications. Just wonder if theres a way to make sure its active before running, say... copy II+
>
> I suggest you leave the standard /RAM driver in place and install the AE driver in a different slot/drive location. That way, 128k software will only disconnect the standard /RAM driver, and correctly reconnect it when its done using the Auxilary bank.
I will have to check the docs on the floppy, but I don't think it'll let me do that..
|
|
|
Re: Ramworks Ramdrive [message #375240 is a reply to message #375220] |
Thu, 01 November 2018 04:48 |
|
Originally posted by: James Davis
On Wednesday, October 31, 2018 at 5:14:46 PM UTC-7, Anthony Adverse wrote:
> Hey there and todays weirdo question is...
>
> How to reconnect a RAMdrive after some bonzo piece of software has disabled it.
What program are you referring to, specifically? Is it Cat Doctor? If so, use it without the Cat Doctor Extension.
|
|
|
Re: Ramworks Ramdrive [message #375241 is a reply to message #375220] |
Thu, 01 November 2018 05:22 |
|
Originally posted by: Anthony Adverse
On Thursday, November 1, 2018 at 11:14:46 AM UTC+11, Anthony Adverse wrote:
> Hey there and todays weirdo question is...
>
> How to reconnect a RAMdrive after some bonzo piece of software has disabled it. I'm using the AE software that allows you to allocate everything over 64k to the ramdrive. But the volume keeps disappearing in certain applications. Just wonder if theres a way to make sure its active before running, say... copy II+
>
> A
Well let me see... AE ProDrive thats all it says, and its "manual" makes it look like an also ran after the DOS3.3 RAMDRIVE software. Perhaps theres a better version of this, I hadn't thought about that to much.
|
|
|
Re: Ramworks Ramdrive [message #375242 is a reply to message #375241] |
Thu, 01 November 2018 05:23 |
|
Originally posted by: Anthony Adverse
On Thursday, November 1, 2018 at 8:22:05 PM UTC+11, Anthony Adverse wrote:
> On Thursday, November 1, 2018 at 11:14:46 AM UTC+11, Anthony Adverse wrote:
>> Hey there and todays weirdo question is...
>>
>> How to reconnect a RAMdrive after some bonzo piece of software has disabled it. I'm using the AE software that allows you to allocate everything over 64k to the ramdrive. But the volume keeps disappearing in certain applications. Just wonder if theres a way to make sure its active before running, say... copy II+
>>
>> A
>
> Well let me see... AE ProDrive thats all it says, and its "manual" makes it look like an also ran after the DOS3.3 RAMDRIVE software. Perhaps theres a better version of this, I hadn't thought about that to much.
Oh, I've been using said beast with Apple Access (boo hiss), copy II+, and basic system. When you swap from one to the next you never know if the RAMdrive will be there.
|
|
|
Ramworks Ramdrive [message #375247 is a reply to message #375220] |
Thu, 01 November 2018 07:13 |
|
Originally posted by: Delfs
Easy answer? Reboot. Most software was designed to unapologetically take all resources from the computer, assuming a reboot on exit, even if it exits ProDOS cleanly/correctly. A reboot ensures that nothing got stepped on, even if the ram drive looks Ok.
Set up an executable to reconnect the ram drive and initialize it and launch your copy program instead of just lunching the copy program.
Perhaps instead of an aux ram drive, consider a using a Slinky card or ProDOS volume called /ram with a newer flash storage option and just pretend it’s memory. :)
Thanks!
|
|
|
Re: Ramworks Ramdrive [message #375251 is a reply to message #375241] |
Thu, 01 November 2018 09:18 |
mdj
Messages: 301 Registered: December 2012
Karma: 0
|
Senior Member |
|
|
On Thursday, 1 November 2018 19:22:05 UTC+10, Anthony Adverse wrote:
> Well let me see... AE ProDrive thats all it says, and its "manual" makes it look like an also ran after the DOS3.3 RAMDRIVE software. Perhaps theres a better version of this, I hadn't thought about that to much.
ProSEL also has a Aux Ramdisk driver, but you can move the AE drive with the Slotchanger utility.
Better yet, get yourself some modern storage and stop using ramdrives :-)
|
|
|
Re: Ramworks Ramdrive [message #375290 is a reply to message #375247] |
Thu, 01 November 2018 17:22 |
|
Originally posted by: Anthony Adverse
On Thursday, November 1, 2018 at 10:13:33 PM UTC+11, Delfs wrote:
> Easy answer? Reboot. Most software was designed to unapologetically take all resources from the computer, assuming a reboot on exit, even if it exits ProDOS cleanly/correctly. A reboot ensures that nothing got stepped on, even if the ram drive looks Ok.
>
> Set up an executable to reconnect the ram drive and initialize it and launch your copy program instead of just lunching the copy program.
>
> Perhaps instead of an aux ram drive, consider a using a Slinky card or ProDOS volume called /ram with a newer flash storage option and just pretend it’s memory. :)
>
> Thanks!
That'd be great, but I was trying to download stuff to it, and I've been unable to copy it off a again, making it... well less than useful. It gets reset after a reboot.
I do have a CF option on order, but you know, have to forge ahead in the mean time. I'd love a slinky.. but haven't seen any.. a ramfactor/charger always captured my imagination back in the good 'ol days.
BTW: I started using the ramdrive to get transfer latency times down during writes to floppy. It didn't seem to help much though. I still can't get anything useful across with this antique Apple Access. Waiting for ProTERM
|
|
|