Welcome, Guest. Please login or register.

Author Topic: help to make OWN "ram:" device  (Read 8294 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: help to make OWN "ram:" device
« on: May 08, 2004, 01:16:27 PM »
Quote
I really need to make an OWN ram-device/-disk, because if I'm not mistaking even if I break WB as soon as it starts downloading, it still has download stuff into the mem cos when I do an "avail" I see approximately 800k+, this, when I have 1024K mem, so I figured if I format a disk and just create needed directorys/files ONLY (for a well functioning ram-device and a few dos-commands there should then be ebnough ram left to download an adf-image (about 911k) to write to disk, right ?

Wrong. Ram Disk is not device, but handler. Also Ram Disk is dynamic, it doesn't take any memory if empty.

The memory lost initially is used by the system itself.

Quote

This is really redicilous, how the hell should I overcome this

Buy more memory?

Other than that there are some tricks, like not copying ENV: to RAM at all. This should leave some more memory to system, esp if ENVARC: is crowded.