Archimedes floppy files

[mist-devel]

Archimedes floppy files

It’s not an Amiga adf file. It’s acorn adf. Use ArcEm or Arculator

…

Sent from my iPad

On 11 Jul 2018, at 04:09, Galbi3000 ***@***.***> wrote: In the instructions for setting up for Acorn Archimedes you state the following: "Floppy disk images ADF format and of exactly 819200 bytes in size are currently required." How do I make those? I have WinUAE and it will only create specific fixed sizes, none of which are 819200 bytes! The closest is "Create Standard Disk" with "3.5" DD (PC)" selected which creates a disk file of 737280 bytes (720KB). The next closest is "Create Standard Disk" with "3.5" DD (PC)" selected, creates a disk file of 901120 bytes (880KB). After that all the other options are too big apart from one that is smaller than the 3.5" DD (PC) one. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Galbi3000]

OK, I got an Archimedes blank floppy image from an Archimedes archive web site and copied that as floppy0.adf and floppy1.adf but the core fails to start up, just a black screen.

Which version of RISC OS?

…

Sent from my iPad

On 18 Jul 2018, at 01:31, Galbi3000 ***@***.***> wrote: OK, I got an Archimedes blank floppy image from an Archimedes archive web site and copied that as floppy0.adf and floppy1.adf but the core fails to start up, just a black screen. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Galbi3000]

I have a number of versions ranging from 3.0 to 3.6 but I used the 3.0 version for MiST as the Wiki says that version was tested and known to work with the core.

Nothing above 3.0 will work. 2.0 and 1.x will. 3.6 is not for the Archimedes

…

Sent from my iPhone

On 18 Jul 2018, at 01:59, Galbi3000 ***@***.***> wrote: I have a number of versions ranging from 3.0 to 3.6 but I used the 3.0 version for MiST as the Wiki says that version was tested and known to work with the core. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Galbi3000]

The notes for the Archimedes core ( https://github.com/mist-devel/mist-board/wiki/CoreDocArchimedes ) state that only RISCOS 3 supports VGA, that suggests to me that version 3.0 at least has been tested. That's the version I used, not 3.6! Yes I said I have versions 3.0 through to 3.6 but I also said I only used 3.0

I know. I wrote the core ;) RISCOS doesn’t default to VGA. Try plugging headphones into the audio jack and see if it “beeps”. If so hold down 0, 4 or 5 on the numeric keypad during a cold boot. That’s how the OS figure out mode to boot in

…

Sent from my iPhone

On 18 Jul 2018, at 03:32, Galbi3000 ***@***.***> wrote: The notes for the Archimedes core ( https://github.com/mist-devel/mist-board/wiki/CoreDocArchimedes ) state that only RISCOS 3 supports VGA, that suggests to me that version 3.0 at least has been tested. That's the version I used, not 3.6! Yes I said I have versions 3.0 through to 3.6 but I did say I only used 3.0 — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Galbi3000]

I put it on it's own SD card with the following files:
core.rbf 319 KB - Archimedes core
riscos.rom 2048 KB - RISC OS 3.0 ROM
floppy0,adf 800 KB - Blank Archimedes disk image from Archimedes archive web site
floppy1.adf 800 KB - Another blank disk image.
And a folder with a few Archimedes game disk images from that same archive site.

At boot the red LED flashes while it reads the core, I hear the audio pop as the machine resets the audio. No beep, no display. Nothing, not even the red or amber LEDs flashing for an error :/

I will try to get hold of a 2.0 ROM image and try that.

[Galbi3000]

P.S. This is where I got the blank disk image from: http://acorn.revivalteam.de/?site=Downloads

The blank disks will not make a difference to this issue. Something is wrong

…

Sent from my iPhone

On 18 Jul 2018, at 19:14, Galbi3000 ***@***.***> wrote: P.S. This is where I got the blank disk image from: http://acorn.revivalteam.de/?site=Downloads — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Galbi3000]

Same result with RISC OS 2.0 ROM

Then there is some issue with your MiST. Some of the newer ones had different RAM IIRC?

…

On Wed, Jul 18, 2018 at 7:27 PM, Galbi3000 ***@***.***> wrote: Same result with RISC OS 2.0 ROM — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPNmYo4hWkQwEIFoweBi_OR6RR_LAffks5uH337gaJpZM4VKVsi> .

-- Stephen Leary

[Galbi3000]

I would not know, I just got it about 10 days ago from Lotharek's Lair web site. Model 1.3 with metal case.

[Galbi3000]

One thing I have noticed is that ALL documentation assumes the MiST is the older model without MIDI ports. One difference in the documentation is that the docs say the red LED should flash error codes but mine it seems to be the amber one doing that function!

I’ve only ever seen the early prototypes built by Till by hand. Never seen a later model.

…

Sent from my iPhone

On 18 Jul 2018, at 19:46, Galbi3000 ***@***.***> wrote: One thing I have noticed is that ALL documentation assumes the MiST is the older model without MIDI ports. One difference in the documentation is that the docs say the red LED should flash error codes but mine it seems to be the amber one doing that function! — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[harbaum]

The MIDI part wouldn't make a difference with any core. It's just not used in most cores.

The RAM chip did change as the old one wasn't available anymore. However, both have identical specs which usually doesn't make a difference. But sdram timing is quite delicate and some cores are operating the ram a little outside spec violating setup and hold times by a few picoseconds or so. That's where the ram chip may make a different as it's unspecified how they react on this.

The acorn core and also the msx core are known to be a little bit tricky here. I have recently been told that increasing sdram drive power from 4 to 8 mA gains a few ps. That may actually help ....

[hubersn]

I am a bit confused about

Nothing above 3.0 will work.

Surely you mean 3.1x? I have successfully used RISC OS 3.10, 3.11 and 3.19 (the German variant) without problems.

Currently I wonder about how CMOS is implemented (or if it is implemented at all, it seems to lose all configure'd stuff after reboot). I was not successful in forcing the core to anything that would drive 1 15kHz screen, because a configured monitortype is thrown away, pressing the key on the numeric pad on boot does not work and I don't know where in the RISC OS ROM the CMOS defaults are stored (or if they are programmatically created somewhere).

[hubersn]

OK, found the CMOS content in cmos.mif in the Archie sources, which explains where the default values are coming from.

[terriblefire]

Read the RISCOS docs. You can hold down various keys at startup to reset CMOS settings for VGA etc.

[hubersn]

Read the RISCOS docs. You can hold down various keys at startup to reset CMOS settings for VGA etc.

Have you actually tried to do this? It never worked for me on MIST. And CMOS settings changed by configure commands are not saved back - there is no CMOS file, and the ROM is (thankfully!) not updated.

It could in theory be a timing issue with my USB keyboard of course that early keypresses are not correctly reported to the core. No idea about the inner workings of either the Archie Core or how MIST firmware deals with the USB side of things.

Yes. It works until you power down and back on again. Between power cycles use Ctrl break to reset and get the cmos changes

…

Sent from my iPhone

On 15 Feb 2019, at 11:09, hubersn ***@***.***> wrote: Read the RISCOS docs. You can hold down various keys at startup to reset CMOS settings for VGA etc. Have you actually tried to do this? It never worked for me on MIST. And CMOS settings changed by configure commands are not saved back - there is no CMOS file, and the ROM is (thankfully!) not updated. It could in theory be a timing issue with my USB keyboard of course that early keypresses are not correctly reported to the core. No idea about the inner workings of either the Archie Core or how MIST firmware deals with the USB side of things. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[gyurco]

Lot of changes happened in the Archie core since this issue opened, I think it can be closed.