rc bug/not working

[cbk1994]

Originally Posted by scriptless

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.

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.

[Crow]

Originally Posted by cbk1994

(or at least they used to)

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:

Originally Posted by Reputation

I agree with scriptless, BSoD doesn't necessarily mean faulty hardware. It's just a critical error that it cannot recover from.

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.

[scriptless]

Originally Posted by cbk1994

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.

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.

Originally Posted by Crow

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.

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

[Crow]

Originally Posted by scriptless

Microsoft, the only OS that told me "keyboard not detected, press any key to continue"..

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

Originally Posted by scriptless

simply put BSoD is a critical error.. as i said when you tried to correct me..

Originally Posted by you

Not like microsoft never messes up. BSOD and RROD are probably the 2 biggest microsoft error's of all time world wide.

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

[scriptless]

Originally Posted by Crow

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..

[Crow]

Originally Posted by scriptless

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..

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.