Modified TOS to remove resolutions limitation

[thorsten.otto]

The "modes" to go TO are actually VDI handle IDs or something like that

It's the device ID, the one that you get by setting workin[0] to Getrez()+2 in the call to v_opnwk(), as the Compendium recommends. ID 1 means "current resolution". zero is not valid i think.

[exxos]

I may sound dumb, but isn't there a unused register in the shifter you can use and just use that register to switch the mono pin ? All you would need TOS wise is to enable High res in the menu and set the new register to switch to mono...

[Smonson]

It's the device ID, the one that you get by setting workin[0] to Getrez()+2 in the call to v_opnwk(), as the Compendium recommends. ID 1 means "current resolution". zero is not valid i think.

Ah right - that makes sense

[Smonson]

I may sound dumb, but isn't there a unused register in the shifter you can use and just use that register to switch the mono pin ? All you would need TOS wise is to enable High res in the menu and set the new register to switch to mono...

That's definitely a backup plan, but it's not as ideal as just having TOS do it in the first place. I'd also like a way to enable 320x200x256 for 16MHz machines one day and the same mechanism would be used there.

[exxos]

I may sound dumb, but isn't there a unused register in the shifter you can use and just use that register to switch the mono pin ? All you would need TOS wise is to enable High res in the menu and set the new register to switch to mono...

That's definitely a backup plan, but it's not as ideal as just having TOS do it in the first place. I'd also like a way to enable 320x200x256 for 16MHz machines one day and the same mechanism would be used there.

Troed I think had a patched driver to do that when he did the 16mhz mod.

https://www.exxosforum.co.uk/forum/viewt ... =110#p8331

[Smonson]

Troed I think had a patched driver to do that when he did the 16mhz mod.

Yeah. We were just unfortunately never able to get his double-speed machine running with the FPGA mod. But he wasn't able to select the new modes from the Desktop Preferences menu, I assume he was running a small utility in AUTO or something like that to set up the extra-big modes after the machine booted up.

[exxos]

What I was hinting at, was you seem to be trying to get TOS to open a new workstation ? If so, thats what the over scan software does.,,

EDIT:
Since TOS does all the work anyway when it detects the mono pin, might you recode that routine so instead of TOS checking the mono pin, it checks the selection in the desktop menu ?

[Smonson]

What I was hinting at, was you seem to be trying to get TOS to open a new workstation ? If so, thats what the over scan software does.,,

I see. No, it's opening whatever default physical workstation it needs at boot time, I just want it to do that successfully without crashing. The next thing I'm going to do is have a bunch of status variables that I can use for holding debugging info, and a little program to print it out.

[Smonson]

Since TOS does all the work anyway when it detects the mono pin, might you recode that routine so instead of TOS checking the mono pin, it checks the selection in the desktop menu ?

I tried it, but I always see a bus error (2 bombs) and an infinite reset loop if I set it up that way. I don't know why.

[exxos]

I tried it, but I always see a bus error (2 bombs) and an infinite reset loop if I set it up that way. I don't know why.

I can only assume if you set up a software register, that tos is checking for that as a physical register, as in hardware, not software ?