Denial

Incredible - still can't believe this runs on a Vic-20

Great work.

@Vic20-Ian: thanks

Mike pointed out that there are drive numbers for devices, so you can have device 8 with drive 0 and 1 and to address a specific drive you have to write "S0:foo" to scratch foo instead of "S:foo".

I did not know this (or forgot about it) and two books on the 1541 don't mention it, one is the C= 1541 user manual (german version).

Do many programs actually use the drive number for disk access?

Wow! Very cool.


Bit by bit we have a real DOS for the RAM disk.

Diddl wrote:Bit by bit we have a real DOS for the RAM disk.

I wouldn't go too far with emulating a real DOS. I just want to put enough functionality in that you can use file browsers and other disk related programs without problems. Of course, if anything is needed by somebody using it in his program, please let me know.

I know a few file browsers and will have a look, if they work with the RAM disk. And I would really appreciate, if some of you did a quick check, if the RAM drive works with your favourite programs and tell me if not. Thanks!

It should be quite stable now, although some bugs always remain.

Kananga wrote:There is a new release of the RAM DRIVE that adds support for the command channel (15). You can now read the status of the last operation, and scratch and rename files.
The driver should survive a reset, if the module area remains untouched.

Download RAM DISK 0.7 here

Running on real hardware as device 9 with the GUI:


EDIT: unnecessary quotes removed.

wow - very impressed - hope to get my FE3 soon.

Hi all!

There is a new version of the RAM Disk Driver available in the download section: 0.8

Storing/Retrieving data, Scratch & Rename should be quite stable.
REL file support is experimental, i.e. feature complete but probably buggy.

Have fun!

Here's a file based disk copy program, which can be used to transfer the contents of a *.d64 or *.d81 disk image to the FE3 RAM-Disk (download): You just need to specify the device numbers of source and destination drive. The program then works through the entire directory of the medium in the source drive copying all PRG, SEQ and USR files. REL files are omitted, and direct access blocks are also not copied. Provided all data (except REL files) is accessible as files, the program can also be used as disk copier with either two real CBM disk drives, or as single drive disk copier with the FE3 RAM-Disk as temporary storage.

Maybe that program gives a little incentive for more people to test their programs with Kananga's FE3 RAM-Disk.

Greetings,

Michael

Mike wrote:Here's a file based disk copy program, which can be used to transfer the contents of a *.d64 or *.d81 disc image to the FE3 RAM-Disk (download):

Thanks, Mike!

Mike wrote:Maybe that program gives a little incentive for more people to test their programs with Kananga's FE3 RAM-Disk.

Perhaps, everybody else waits until you found all the bugs and I fixed them.

All features are now implemented and I am proud to announce the official release of the RAM disk: 1.0.0

So what do you get?

You can load and save files from and to the RAM-Disk slightly faster than using SJLOAD and SD2IEC. Since that also comes with the FE3 and of course all data in RAM is lost if you switch of your VIC-20, this is in itself not worth much.

But, if you want to write a program that runs on real hardware and needs to load additional data, the RAM disk offers speed and compatibility with certain important features of the original hardware.

One situation where the RAM disk comes in handy is when programs need to load additional data from a fixed location, while being able to switch to other disks (or directories) for other operations.
On original hardware you would need two disk drives: One holding program data and the other the user data. Using the RAM disk you could copy all program data to RAM and use the SD2IEC for user data and still build a program that can run on original hardware (e.g. using two 1541s).

For example, you may have a game which sometimes needs to load level data. You could store the data in a REL file and use it on demand. Fortunately, the RAM disk supports REL files almost like a 1541 would, which allows you to write programs for both settings.

If you do not care about compatibility to the 1541, you can also use the "P"osition command for random access to any other file in a way compatible with SD2IEC.

In order to make integrating the RAM disk into your project easier, the initialisation routine looks for a program called "RDRUN" and, if found, loads and runs it instead of returning to the BASIC prompt. That way, you can write a program that loads the RAM disk from a boot loader before executing your own initialisation code.

Please let me know, if you need anything else to make the program useful!

Otherwise this is the final release.

Have fun!
Kananga

cool, thank you!

Anyone got a download of @Kananga ramdisk?

Some time ago, Kananga moved his file repository to sourceforge: https://sourceforge.net/projects/vin20/files/

Here's the link to the *.zip of FE3 RAM Disk V1: https://sourceforge.net/projects/vin20/ ... p/download

Cheers,

Michael

Kananga wrote: EDIT:
You could also write a program that copies a whole disk in one go, by storing the image in the RAM drive! But who does still use real 5 1/4'' disks?

...me. I use tapes too, often more than disks.

Javier, Sven - FYI, I split off the recent discussion to the new thread "Using FE3RD in VICE (was: Re: FE3 RAM Disk)".