Hi Pat,

> ..yep I'm running AMD64 cpu and 64bit version of Ubuntu Hardy (8.04).
> For some reason I cannot get hard disk images to work. I've downloaded
> from the ArcEm site the 20Mb and 64Mb formatted images and called them
> 'HardImage0' and 'HardImage1' respectively.

Yes, they're the correct filenames for the first two drives.

> I then updated my './arcemrc' with (hopefully) the correct disk
> params. Thus:-
> 
> ==
> MFM disc
> 0 612 4 32 256
> MFM disc
> 1 1024 8 32 256
> ==

`strace -e trace=open ./arcem' suggests it's reading
/home/ralph/.arcemrc for me, not ./arcemrc, so your disk params aren't
being seen at the moment.  Yeah, I know, $PWD for some files, $HOME for
others.

> Now one of my goals here is to get ArcEm running the 'ELITE' game. So
> I also downloaded an ".arc" image of it here:-
> 
> http://www.iancgbell.clara.net/elite/arc/index.htm
> 
> and renamed it to 'FloppyImage0' in my arcem directory.

OK, b5052410.arc is a !SparkFS image, in other words, the equivalent of
a ZIP or tar.gz in the RISC OS world.  It's not a floppy image.  There's
also b5052420.zip for download off that page and that contains ELITE.ADF
which is an 800KiB floppy image, suitable for calling FloppyImage0.

> floppy format ADFS 800KB used for drive 0's r/w, 428909 length, image.
> inserting floppy image FloppyImage0 into drive 0: ok
>
> From the above, it appears to have detected the drive 0 and drive 1 -
> only giving errors for drive2/3. But I cannot access them from ArcEm
> GUI.

The ./hexcmos file from CVS seems to define no floppy drives and one
hard disc exist.  IOW, auto-hardware detection didn't exist on these
machines, you used to change the setting in battery-backed RAM.  To
change this, you can run !Configure under Apps IIRC and then increase
the number of Floppies to 1 and ST506 drives to 2.  You should then see
a floppy drive on the icon bar, click that to give a Filer window
showing !elite, double-click that to put it on the icon bar, and then
click it there to start the game.

> I also see (as pre previous posters in this list) the following:-
> 
> ==
> Read data command exiting due to failed file seek
> seek: cylinder address greater than or equal to configured, 0 >= 0
> ==
> 
> ..but I don't know if this is referring to the HardImage0/1 (which is
> present) or HardImage2/3 - which is not configured.  Can anyone help
> with this error message?

If you still get it after setting up ~/.arcemrc, let us know.

> BTW: I have ROM image 3.10 (I think) which I managed to track down
> after extensive googling/newsgroups (sigh) here's the byte count:-
> 
> ==
> -rw-r--r-- 1 patb patb 2097152 2008-10-29 12:33 ROM
> ==

Run sha1sum(1) on it and see if it matches one of these digests.

    arthur-0.30.rom  6aebd686d97dfdf6726fa5f3246ef35b840b286d   524288
    arthur-1.20.rom  1181ff9c2c2f3d6d414054ec33b2260404bafc81   524288
    riscos-2.00.rom  b82a78830dac386f9b649b6d32a34f9c6910546d   524288
    riscos-3.00.rom  b4fa494d51dd704c9da9653c2acc6acd08cc8cf4  2097152
    riscos-3.10.rom  68533e0a93657a879c1697c04f32d517345b1a61  2097152
    riscos-3.11.rom  3487729e87bebc9cb51665838c27beff22f7b3bd  2097152
    riscos-3.19.rom  ba8c7abe0e6c6c5d7138481c6c052425cbc8b8f4  2097152
    riscos-3.50.rom  c31318e712ee7de92e46f9df6c791b614d4c9304  2097152
    riscos-3.60.rom  3cf75aa4d4dc8fe57110a124fbd1560d46c549b1  4194304
    riscos-3.61.rom  71e67684e1d22f422ab9c586c6b0f900384e8f14  4194304
    riscos-3.70.rom  42c3dd0ae43149849b674ea025cb2206512a5b4a  4194304
    riscos-3.71.rom  c5fe0645e48894fb4b245abeefdc9a65d659af59  4194304
    riscos-3.80.rom  7e461a6aeb9b1cdc03ea734d0c3a9e1a65d3f98a  4194304
    ncos-1.06.rom    4400bd142eebdc71b7ac1794f2cf7dc39de983e2  4194304
    ncos-1.11.rom    7c9e2039bc096038ab236719211a236e9a28192f  4194304

    arthur-0.30.rom  MOS Utilities   0.30 (17 Jun 1987)
    arthur-1.20.rom  MOS Utilities   1.20 (25 Sep 1987)
    riscos-2.00.rom  MOS Utilities   2.00 (05 Oct 1988)
    riscos-3.00.rom  MOS Utilities   3.00 (25 Sep 1991)
    riscos-3.10.rom  MOS Utilities   3.10 (30 Apr 1992)
    riscos-3.11.rom  MOS Utilities   3.11 (29 Sep 1992)
    riscos-3.50.rom  MOS Utilities   3.50 (18 Feb 1994)
    riscos-3.60.rom  MOS Utilities   3.60 (13 Apr 1995)
    riscos-3.70.rom  MOS Utilities   3.70 (30 Jul 1996)
    riscos-3.71.rom  MOS Utilities   3.71 (19 Feb 1997)
    riscos-3.80.rom  MOS Utilities   3.80 (28 Apr 1998)
    ncos-1.06.rom    MOS Utilities   4.50 (26 Oct 1996)
    ncos-1.11.rom    MOS Utilities   4.50 (26 Oct 1996)

When you get to a `*' prompt for the CLI, e.g. F12 from the Desktop, the
command `fx0' should print out the OS version too.

> BTW(2): I have also tried 'linux32 ./arcem' to force 32bit linux on my
> AMD64 - did not see any difference :-/

Well, at least that means it's not a tricky 32/64-bit problem.  IIRC,
Dr. David Gilbert, the original author, developed it on a 64-bit DEC
Alpha, but the hands that followed, like mine, might not have been so
careful.

Cheers,


Ralph.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
arcem-user mailing list
arcem-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/arcem-user

Reply via email to