Hi Rob,
> > > MFM disc
> > > 1 1056 16 63 512
> >
> > The `drive number' is in the range 0..3 so drive 1 would be drive 5
> > under ADFS. Perhaps that's it.
>
> Ah that might do it...
>
> I'm trying to get the HardDrive Image from my A5000 into the emulator.
> I have a 520MB harddrive that I have made an image to an NFS drive
> using FCFS. However, when I tried that, it didn't work at all, the
> emulator died just after the desktop started.
What OS are you running the emulator on? Did it give any kind of
diagnostic when it died or the OS killed it?
I'll have a look and see where FCFS puts its meta-data. IIRC it's
appended to the disc image so programs can use the bytes at the
beginning of the file as a disc image without problems. But perhaps it
has an option to `compress' unused sectors or something.
> Reading around, I thought I'd try a smaller disk, which I hooked up to
> the Arc and formated as 959, 8, 63. This I loaded with the stuff I
> wanted, but couldn't get the emulator to work
Again, some more clues about how it didn't work would be helpful.
> until I stuck:
>
> MFM disc
> 1 1858 8 48 256
>
> In the config file.
How does cylinders, heads, sectors, and sector size of 1858, 8, 48, 256
correspond to a drive formatted at 959, 8, 63?
> It seems to work better, but I still get lots of:
> Seek - cylinder address greater than specified (=1035)
> Seek - cylinder address greater than specified (=1066)
> Seek - cylinder address greater than specified (=1069)
> Seek - cylinder address greater than specified (=1075)
> Ad infinitum, while I'm using it.
This error comes from arch/hdc63463.c. The seek command being given to
the hard drive controller is requesting a cylinder number, the one given
in the error message, that's greater than the number of cylinders given
in the most recent `specify' command. There's some DEBUG in the
SpecifyCommand() function that you could turn on to see what dimensions
the OS is supplying to the controller. It presumably gets these from
the first few sectors of the disc image and they're set up at format
time.
Better still, and I'll check this into CVS when I've Internet access,
change the error message from
fprintf(stderr, "Seek - cylinder address greater than specified
(=%d)\n",DesiredCylinder);
to
fprintf(stderr, "seek: cylinder address greater than specified, "
"%u > %u\n", DesiredCylinder, HDC.specshape.NCyls);
> I also haven't worked out how to get it to start the !boot sequence on
> startup.
`*Configure Boot' once in the emulator? That should cause the `hexcmos'
file to be re-written, storing the new value.
> I did manage to load Style onto it, which was my main purpose.
>
> Now, my aim, is to be able to produce and get to postscript versions
> from style. I will probably setup a postscript printer, but what are
> the easy ways of getting the information onto a linux partition? How
> do people do this?
I'd use a DOS format floppy image and use mtools, or mount it using the
loop-back device. Note, I wouldn't have it mounted and have arcem
accessing it at the same time.
> Can I create a 50MB msdos format hardddrive and use it with the dosfs
> module?
I can't remember enough about how ADFS/DOSFS works to answer this but
I'd guess in theory it should be OK assuming RISC OS gives access to a
DOS hard drive normally.
> I don't think a floppy image is going to be big enough. I have a
> syquest 230MB disk, that I loaded drivers somewhere into the boot
> sequence, that could read a dos format syquest, so I probably have the
> correct modules somewhere. If only I could remember back to 1999 when
> I used to use the Acorn.
:-) Hope this helps some.
Cheers,
Ralph.
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
arcem-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/arcem-user
