Usual STOS fixers add new tables for later TOS versions. I solved it different: mouse read is via VDI, joystick read is via Joyvec - and code what works on all TOS versions is really short - total some 40 bytes. Why good programmer(s) of STOS were not aware of that way ? I can think only 1 reason -...

As said it works in all TOS versions 1.00-4.04 . I don't care for MagiC, Mint etc ... It is not first case that I used TOS function without proper docs, but instead it traced it - what was common practice in past too by programmers. Now, if you think that what stays in DOCs is more important than w...

Hatari gets the mouse position change and/or relative mouse movement events from SDL, so it's unlikely to be Hatari problem. Problem can be related to fullscreen resolution being (much) smaller than the laptop screen resolution, and your trackpad driver (and/or SDL) not handling that correctly. SDL2...

Looking at Hatari sources, the STE bus emulation indeed just removes bus errors for several HW register address ranges, nothing else. But it's a lot more than just that address range you indicated. If you think about how this would be implemented in HW, it's fairly cheap way to get a bit more compat...

How many of the people around you have Android phone (i.e. Linux based OS) instead of Windows phone? While traditional Linux desktop distros are indeed around ~1% of OS usage (and unlikely to never gain more), Android also uses Linux, as does ChromeOS. And as I stated earlier, Android's OS usage sha...

I think that here you are seriously wrong. How you know that worked for everybody else ? In case it wasn't obvious, everybody else who has reported to have tested Hatari Windows version, has told it to work fine. Yes, I did lot of diverse tests, but you again come with ridiculous assumption (well, ...

Not getting feedback about not working in Win 7 ? There was actually one, in 2.0.0 thread, right before mine. If you refer to: http://www.atari-forum.com/viewtopic.php?f=51&t=30676&start=50#p332676 "amilo3438" clearly says its on XP, not on Win7. SDL2 was first released 3 years af...

So 1: not too good idea to put untested stuff in such archive. As I explained earlier, that's the whole point of auto-builds. It's a service from one Hatari user to other Hatari users, to help them help testing Hatari. Alternative is that we don't provide Windows binaries (until somebody steps up t...

It is not about that it did not work for me. How many times I need to repeat that I'm not only one Win 7 user ? If did not work for me, it did not work for hundreds of others. But you just repeat same and same - for how many people it worked :D You're the first one to report an issue, and as things...

Just my 2 cents worth here - AtariZoll you tend to write longer posts than usual - very long posts actually. ... I understand that this isn't 100% your own fault, but perhaps think about breaking a long post out into a new thread - just like you've done here. Agree, splitting things into separate t...

So, thothy said that "just state it once in a polite fashion and then shut up" :mrgreen: I guess 'shut up' is polite. And yes, this is good example where I have communication problem with SOME people. In polite fashion ? No, as I said I was angry. That site is not polite, Hatari team Wind...

Regarding Hatari v1.4. It was still using the old UAE CPU core, not the new WinUAE CPU core. The old UAE CPU core completely lacks emulation for following 030 features: - instruction & data cache - 32-bit access - MMU And it was also otherwise much more inaccurate. Because of these omissions, it...

BTW I wanted to ask you about Hatari symbol loading direct from the Atari binary - as it has trouble with the new binaries - I can't use the NM route anymore because the symbols direct from ELF have different offsets from those in the final TTP. So it would be good to figure out if its a problem wi...

For ST/STE -only programs, only options for freely scaling the window is SDL2 build of Hatari 2.x. Note that when running ST/STE games on Falcon, they can work better if you run first a program that: * disables 030 caches * sets Falcon to STE bus compatibility (0xff8007 register) & 8Mhz mode (8M...

The VoxxFree version (voxx_100.prg) here: http://www.axxim.de/r3dias/R3_Vocoder3.htm Is the one that freezes. The earlier voxxdemo.prg version starts fine in Hatari though. I don't have a mic with which to test it, but from the sounds it gives without one, I don't think the DSP processing is working...

Dang, the forum SW is acting again, it's revealing the "secret" tags. I'm pretty sure I've been targeted by them too, based on few programming itches I had earlier. ;-) Anyway... If you really happen to take a look at the visual debugger, one of the problems of using the same window is tha...

Well, if you're debugging your own code, you can look up the variable types from your sources, or otherwise remember them. Memdump is probably easiest way to look at the values (for 16-bit variable, just take the 4 first hex digits at given address). And if you want to know hex e.g. in decimal, use ...

Yes but I also want to execute additional code to dump my program's state through the Debugger console print functions, a program specific coredump facility. Unless you provide the Hatari debugger with the ability to list my variables correctly with datatypes and readable names ;) If you have symbo...

Yes, I was wondering whether you were considering doing it SDL2-only. Anyway, I'm interest to see your prototype code. :-) (Your screenshot of the other emulator looks really bare bones, I'm not really sure whether something that primitive would be any kind of improvement over current console debugg...