help to make OWN "ram:" device

[GreatLor]

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 ?
However, the other part of the story getting better and better (read 'worse and worse'), last time I had this problem with a adf2disk progg that required OS 2.0+, so I download another one, now this one requires something about 3.9+ (?)  :lol:
now I dont even DARE thinking about more adf-/image-2disk stuff  :-)

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

[GreatLor]

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.[/quote]

hmm... , thats why I wanted to make a new ram-devi.. uhh I mean ram-handler, hehe, the WB-startup-sequence looks like a real mess ( :-D ), so can you come up with a script to take care of this problem man ? I would really be thankful If I could have say 960k+ ram when in cli  :-)

[GreatLor]

ChaosLord wrote:
It is 2004.

Hard drives have been available for Amiga since 1986.

Buy a hard drive.

Wow, such great assistance some ppl give !!!

If you totally delete or rename startup-sequence, you'll directly end in the CLI window and have as much free RAM as possible.

Thank you Thomas.
By the way I looked in startup-sequence yesterday and noticed something weird, when I "break" into CLI at immediately at startup, the line "echo A500/2000 ..." (or something like it) never gets executed, so this ram-handler must be defined in one of the (three ?) first commands before the "echo" command (since it obviously isnt executed), does it mean that those  (three ?) first lines are enough for a functioning ram-handler ? just curious now  :-)

[GreatLor]

Well daaaa !! :-o , need you REALLY tell me that echo just writes text to the screen ? Cheeezes, I wasnt looking for an description on what "echo" is and how it works  :-D , I wondered if those few lines BEFORE it were enough for a functioning ram-handler !
Oh, I cant post you my startup-, I'm not at home.

[GreatLor]

That "ram:" probably wouldnt work without startup-sequence was my very guess.
And no, I dont need a GUI, just 960k+ ram with its handler.

[GreatLor]

Thank you both very much, appreciate it very much.

ps: hey where do you usually buy your amiga devices ? just curious ! (as always  :-) )

[GreatLor]

Yes, I'll post the outcome tomorrow, just hope it'll work, not too optimistic though !  :oops:

[GreatLor]

Darn, it worked, but it gave me 941k  :pissed:
f.u.c.k  :lol: , I just need some 19k more, GRRRR ...
yepp, destiny is truely a funny shot !

[GreatLor]

Are lzh-files extracted with lha ? in that case lets see what the baby can give me ?

You know, I was also wondering if I could remove 1 or 2 dos-librarys that are in the RAM and who do not get accessed unless called from specific dos-commands, I thought if it would be possible to do it by calling the FreeMem-routine in exec.library or are these libs untouchable ?

[GreatLor]

Got the message !  :-)

[GreatLor]

It seems my missfortune has NO PLANS of taking a vecation, guess what now, ok, I go and buy 10 "verbatim" disks, and amiga-format them in the amiga, then I unpack an lha file and copy to the disk, I insert that disk and try to "dir", but no, "not a dos-disk in df0:", I format them again with other formatting tools, it's still "not a dos disk in df0:", now, have anyone ever experienced these "verbatim" disks ?

[GreatLor]

Nope, it didnt work the format command says "bad sector" or something like it, this is REALLY weird !!!  :pissed:

[GreatLor]

Problems ?  8-) , you've seen nothing yet, I'm a guy with EXETREME bad luck, I dont know, it seems the universe doesnt want me !  :-(

I might try a cleaning disk on the A500. Also, see if you can find a known-good 3.25 disk to test with. Verbatim's were fairly good disks back in the day, but lots could have happened to your box of them, since then. I don't think Verbatim has made DS/DD 3.25 disks in about 10 years!

The disks I bought are HD disks.

Anyway could it be the drive which is a problem ? I mean, while there are still a few disks about which the system doesnt complain, however, more and more disks get "read/write error" everyday it seems, so where would I get a cleaning disk ? are the ones for pc fully copatible with A500 ?

[GreatLor]

So where in hell could I get DD disks then ? Is there NEW DD disks sold anywhere ?

I have "FUJIFILM" HD disks who work (some of them have got "read/write error" but this they got when I used them as 1.44 MB floppy disks for the PC), but these verbatim disks wont work.
Where's 89-93 when you need'em ?

[GreatLor]

Is there something wrong with the prices or what  :-o