I'll test on the other PC to see if it works for me.

I tried both versions. And the one for 95/98/ME gives runtime error's UNLESS you run it in compatibility mode for 98/ME.. however then it just says program stopped working before it even worked..

Short of me doing a VMPlayer with windows 7 or XP.. just for rc.. windows 8 is not capable of using external rc..

i think my only solution is linux =/ or going back to windows 7 .. uhg

And yes, its entirely window's fault.. window's isnt even windows anymore.. they should change there name to "metro" now.. since thats the new interface.. at least real windows uses.. windows.. that u can resize... move.. close etc.. heince the name..

and microsoft breaks every one of there products.. at least when stefan programs stuff it works..and if not he fix's it.. he might not add everything we want but for crying out loud hes 1 person not a corporation of employees.

Not in this case, no. Not really GTK's fault either, since there are versions that work well with 7/8. So, rather, it's Stefan's fault.

http://i.imgur.com/LClpf.png
External RC is a nope on my W8P.

I'm saying, GTK didn't change drivers on my PC.. Stefan didn't change code in my RC.. Windows changed, and now we have a problem.. Pretty logical to say it's windows that messed up. Not like microsoft never messes up. BSOD and RROD are probably the 2 biggest microsoft error's of all time world wide.

I am willing to bet you that I can fix this error, without touching the RC, or GTK with any type of hex editor, or modifying it in any other way.

You do know what GTK is, right?


I doubt you can. You seem like the typical "I hate Windows but use it anyway" person, though. Microsoft is not to blame here. If they wouldn't ever change anything, there would be no progress at all. Developers have to adapt, and most of them do. Stefan did not, and won't.

On an unrelated note, you're only getting BSODs if your hardware is faulty (not Microsoft's fault) or if you're an idiot (not Microsoft's fault). Can't comment on RRODs though.

No, you can also get BSOD on software issues.. and yes I do know what GTK is.. I have used it in many crossplatform projects because the Windows API's for graphical interfaces don't work for other operating systems. As for RRoD.. it usually means hardware failure and most commonly wire shortage. People often wrap them in blankets to get them to melt back in place or send them back in.. Point is microsoft makes shitty stuff usually.

And you're pretty much admitting, microsoft made a change that caused it to not work.. period.. yes, ofcourse stefan could make changes to adapt.. but microsoft is at blame for breaking it..our pretty much saying if windows was to completely redesign itself to use totally different style.. like cloning themselves to be a mac.. that it would be stefans fault that it no longer works.. which makes no sense at all? do you see where I am coming from?

Imagine doing math homework in school. You read the instructions on the paper.. you follow them.. you turn the paper in and get an "F" not because your answers are wrong, but because the instructions changed after you turned them in? Who's to blame?

I only use that example, because computers use instructions and microsoft changed them after the fact..

The whole point of an operating system upgrade is that things change. Try running software written for Windows 95 on your old Windows 7 installation and then get back to me. A lot of the stuff is forwards compatible to a degree, but no popular OS claims to maintain total compatibility moving forwards.

Windows, OS X, and most flavors of Linux all change. Windows is honestly the most conservative when it comes to making changes, too. They literally hack program-specific fixes into the OS code (or at least they used to) to keep outdated or poorly-written software from breaking on upgrade. Software on OS X tends to break every few years.

Stefan needs to update RC, it's naive and impractical to expect Microsoft to keep it working forever on an OS that is different than the one it was written for.

As far as I know, they still do.

Windows does change, that's only natural. Your comparison with a test doesn't really make sense either. Let's rather compare this to any machine that is being frequently used. If you don't maintain that every once in a while, it will work less efficient, then stop working at all at some point. Developers don't have to update their software for more recent operating systems, but if they choose not to, things will not run. It's rather simple.


Edit: You could've argued in here, but whatever. I did name two reasons for BSoDs, I believe that qualifies. But alright, let me elaborate: it's either faulty hardware, faulty/incompatible drivers or software which is going farther than it should. In any case, it is usually not Microsoft's case, like way too many people make it out to be.

Yes, but at least Linux (which is just a kernal) based systems usually offer an open source community where YOU can fix it yourself. Microsoft doesn't.

And my point was, a working peice of software was broken because microsoft made a change, not stefan.. everyone here pretty much agree's that microsoft's update broke it.. it's stefan that needs to "fix" it tho.. however, if microsoft hadn't broken it, it would still work.


Microsoft, the only OS that told me "keyboard not detected, press any key to continue".. x_x.. simply put BSoD is a critical error.. as i said when you tried to correct me..

A keyboard is apparently required, so when that pops up, you plug it in and press a key to continue. Simple, is it not?


My point: you're blaming it on Microsoft when you shouldn't.

It's microsoft's way of dealing with the problem is it not? lol and you don't need a keyboard to use a pc.. o.O they have OSK (On Screen Keyboard) for that... and now, more then ever touchscreen..

isnt scriptless the same guy who complained at windows for not being able to play computer games on linux

No? I don't play any other games then Graal, and I used to play SC2 until I overloaded my desktop and damaged a bunch of components.

The only thing other then that I play is Call of Duty on the xbox, which sucks because I liked playing it on PS3 better..

Well, taken into account that the error message is old as hell (probably when mice were not around/not supported) and was, as far as I remember, not even a Windows/DOS error (actually, possibly DOS), but rather one of a specific BIOS (or so I believe)... I hope you know what I'm trying to say. I'll say no more, though, since it's a waste of time.