BlueMSX and ObsoNet setup?

Page 2/2
1 |

By tschak909

Rookie (26)

tschak909's picture

07-11-2018, 07:53

...what...in the hell...am I doing wrong?!

-Thom

By Manuel

Ascended (14738)

Manuel's picture

07-11-2018, 11:53

Is there even something wrong? What did you expect to happen in the end?

By edoz

Prophet (2091)

edoz's picture

07-11-2018, 11:58

I was wondering this as well... I'm not an expert in this but it seems the driver was loaded?

By tschak909

Rookie (26)

tschak909's picture

08-11-2018, 06:42

You should see a message indicating the driver is loaded. If I try to get INL status, it again drops back to MSX-DOS.

I am very surprised, seeing how old INL and ObsoNet is, that people seem to be rather clueless, about it...

-Thom

By tschak909

Rookie (26)

tschak909's picture

08-11-2018, 06:49

well, it seems to work, now... I had to go into Machine Configuration, and insert the ObsoNet BIOS into the machine configuration in a free slot. This is not evident from the BlueMSX documentation, at all.

-Thom

By tschak909

Rookie (26)

tschak909's picture

08-11-2018, 07:15

For anyone who stumbles on this. The trick is NOT to load the BIOS in the cartridge slot (0 or 1), but rather to insert it into the machine's memory map somewhere e.g. slot 2-3, as ROM type ObsoNet.

I now understand that the "double" obsonet message is due to the emulated system loading the BIOS twice due to mirroring.

Once I fixed this, the RAMHELPR and INL handlers loaded correctly, and I was able to see the network and connect to IRATA.

Now I can complete the work for at least the UNAPI version of PLATOTerm.

Here it is working:

-Thom

Page 2/2
1 |
My MSX profile