Search found 553 matches
- Fri Mar 06, 2020 10:21 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
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 ju...
- Fri Mar 06, 2020 10:18 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
Ah right - that makes sensethorsten.otto wrote: ↑Fri Mar 06, 2020 10:04 am 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.
- Fri Mar 06, 2020 9:35 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
Thanks Thorsten. This rebooting problem only occurs when booting up in low res - it seems unrelated to the monitor-change detection. If you want to see the problem it's here: _FindDevice() is called inside v_opnwk() and basically checks that a resolution change is a valid one, and then if it is, it ...
- Fri Mar 06, 2020 1:03 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
I'm still tapping away at it, but the weird thing is that as soon as I add support for changing from low res to mode 4 (high) in _FindDevice(), the machine will no longer boot (it goes into an infinite reset loop) into low res mode - it does boot in hi-res. I'm working my way through v_openwk() whic...
- Tue Mar 03, 2020 10:40 am
- Forum: MONGREL H4 USER BUILDS
- Topic: exxos build
- Replies: 80
- Views: 38793
Re: exxos build
Fantastic!
- Tue Mar 03, 2020 10:37 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
if you just want to prevent a reboot on monochrome monitor change detection, you could change I think that would prevent rebooting, but if my reading of the code is right (can't test with hatari) then the shifter mode register and sshiftmod would still be modified. I skipped the check by changing f...
- Mon Mar 02, 2020 10:31 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
There's clearly a problem with this modification, but I wasn't able to resolve it tonight in the time I had. Sorry, Cyprian. I'll have to give you a raincheck on the details. I'll let you know when I make some progress.
- Sun Mar 01, 2020 12:11 pm
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
I thought the mono_det pin had to be used as it resets the machine. I don't think its possible to simply change resolution as the VDI has to be restarted. I assume that pin forces TOS to reboot. The only way I thought it could work is to enable high res in the menu, then have it flip a bit in a reg...
- Sun Mar 01, 2020 9:22 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
604 actually. But some addresses are duplicate. And the Line-F handler also serves another purpose: to replace the epilogue of most functions. That saves 6 bytes in most of them. And that was the whole purpose of this handler, because the alcyon compiler that was in use was too braindamaged, they r...
- Sun Mar 01, 2020 8:11 am
- Forum: SOFTWARE
- Topic: Modified TOS to remove resolutions limitation
- Replies: 50
- Views: 25739
Re: Modified TOS to remove resolutions limitation
It's worse than you think! Instead of using the standard "BSR" or "JSR" instruction to call a subroutine, 603 commonly-used functions are built into the line-f exception handler. By executing an invalid opcode, the vector is triggered and the opcode is inspected to find out which...