oricutron icon indicating copy to clipboard operation
oricutron copied to clipboard

Cannot start telestrat without drive

Open jedeoric opened this issue 9 years ago • 7 comments

When we select telestrat, it enable microdisk option in oricutron. But, on a real Telestrat, it can start without microdisc. In oricutron, we can not deselect microdisc to start telestrat without the drive.

Priority : very very low :)

jedeoric avatar Jun 13 '16 14:06 jedeoric

Also, testing using a "WIP" version from ISS dated 2018-10-04, it seems there's an issue with the Telstrat disk booting, because I cannot get it to load the "stratsed.dsk" image (The Telestrat just stas 'locked' on the boot screen with the 'insert disk' message...), while it works fine in Oricutron 1.1...

laurentd75 avatar Jan 30 '19 23:01 laurentd75

Well, current version works...

polluks avatar Jan 31 '19 01:01 polluks

I don't have this issue too.

Anyway, it works because the microdisc is connected in Oricutron. I mean this issue is not the same problem than @laurentd75 explains.

The real telestrat can start without a drive connected. It just start with rom without stratsed. Telemon checks if a drive is connected. If it's connected, it tries to read the boot sector.

In order to correct this low issue :), we could remove microdisc in menu when telestrat is started. In this case, telestrat could start without microdisc with telemon inserted.

jedeoric avatar Jan 31 '19 13:01 jedeoric

I's really weird because after @iss000 told me he didn't have the problem in his developer builds and I retried, I couldn't reproduce the problem with either the 2018-10-04 WIP version or his latest version posted on his site. HOWEVER, at the Oric Meet this week-end, we encountered the bug on @TotoShampoin's PC with @iss000 's latest developer build: after "powering" the Telestrat and seeing the boot screen we used the menu to insert the "stratsed.dsk" image into Drive 0 but then nothing happened, the disk didn't boot... There MUST be a particular sequence of events that leads to this bug but I have yet to find the procedure to reproduce it 100%... Also, I sometimes get the issue with Oricutron 1.1...

PS - @polluks: incidentally, looking at your screenshot I see there's a small typo to correct: "SUITE YOUR NEEDS" is misspelt, it should read "SUIT YOUR NEEDS". What's more, "re-modified" doesn't make much sense, "modified" is enough IMHO... :-)

laurentd75 avatar Feb 04 '19 00:02 laurentd75

@laurentd75 How about defining GENERAL_DISK_DEBUG?

polluks avatar Feb 04 '19 09:02 polluks

Hi @polluks is this a runtime option, or a compilation (#define) option ? To be honest, I'm not really familiar with Oricutron's source code and never attempted to compile it myself on Windows...

laurentd75 avatar Feb 04 '19 11:02 laurentd75

The latter, I don't use Window$ at home.

polluks avatar Feb 04 '19 22:02 polluks