64 MB Hard Disk for your Adam!

I have been experimenting with MicroFox’s Floppy Disk Emulator, also known as the Virtual Disk Drive (VDD). Using some software I wrote on my PC I was able to create a 64mb disk image that the VDD would open (64mb is the limit it appears) and then initialize it with EOS and it is recognized as a 64MB disk. The AdamEM emulator on the other hand doesn’t like it, but that is ok.

Here is a copy of this blank, initialized disk image. Copy some files to it, let me know how it works out.

64MB.zip

3 Replies to “64 MB Hard Disk for your Adam!”

  1. OK, I gave this a test drive and was able to save and retrieve a couple of word processing files.

    Then I loaded SmartBasic and did a directory and saw the two files there.

    Then I copied some SmartBasic programs to the 64mb disk, loaded SmartBasic, and was able to run some of the files off the 64mb disk. Some wouldn’t run, but then I discovered they wouldn’t run on the original disk either. There was an inaccurate block count on the 160k disk leading me to believe it was probably incorrectly copied from a ddp.

    It works!!!

    But then it brought up a couple of questions:
    1. How many files can be stored on this disk? On a regular disk there is only room for a certain number of file names in the directory. How big is the directory on this disk?

    2. Is it good for anything else besides storing data or word processing files?

    3. Haven’t tried it yet, but I be believe programs like SmartFiler create a data disk with entries limited by the size of the disk. Would this create a super-large database or would SmartFiler think it was a 160k disk?

    1. I set it up with a 8 block directory which works out to about 315 files allowed with each being 26 bytes and a volume record of 26 bytes. This is more of a proof of concept as this opens yup the admam for more experimentation – no longer are we limited to the size of a diskette.

      1. To any legacy program this would still be seen as an ADAM Disk. So I would imagine programs that create data disks would be limited to how they are hard coded to utilize that disk, if they are using standard EOS directory blocks. There is an old Nibbles and Bits newsletter that recommended not creating directories greater than 3 blocks because ADAM can behave “unpredictably”. Again that is probably referring to older programs expecting a standard DDP or 160K disk as the storage medium.

Leave a Reply

Your email address will not be published. Required fields are marked *