Hi! Frank Naumann wrote:
No, I would never even think about that. I just do not like hacks in new apps because of some other SW imperfections. TSR seems to be the right solution for me in this case. And so far I cannot think of any better.As the XaAES is a kernel module and thus part of the kernel it's for sure fully legal to manipulate caches. I aggree with Ozk that it'smuch better and more user friendly if no TSR is needed, e.g. the TSR is the bigger hack of the two alternatives (and will for sure lead to much more confusion).
There is a binary of the particular driver, right? I don't get why that one could not be patched to do what is required. Or you can even wrap one binary into another and build one single TSR for the VDI you need when you speak about user friendliness.
All right guys we seem really to disagree from time to time. Yet again my point of view:The particular VDI driver is clearly a AUTO VDI (therefore TOS) problem (not MiNT nor AES'). Yes any TSR is a hack of course but until you have the VDI cleanly integrated in the OS - FreeMiNT (which you never would because you would never quite supporting the old dead cards - understandably) - then the VDI all is a hack to the OS (sitting on a trap somewhere in the system which doesn't even know about it strictly spoken). And therefore a TSR would be more appropriate hack as opposed to tweak AES to support every stupid VDI implementation that doesn't do what it should (and it is VDI no matter which particular part of it).
Perhaps someone will someday convince me on te opposite but that doesn't really matter...
STanda