Page 1 of 1
Posted: Thu Dec 06, 2007 5:45 pm
by GORDON
Posted: Thu Dec 06, 2007 6:13 pm
by TheCatt
That's awesome.
Posted: Thu Dec 06, 2007 6:17 pm
by TPRJones
Yep, last night at some point when I rebooted my computer (after installing a Windows update from Microsoft), my system croaked. boot.ini was gone. It was a bit annoying, although easy enough to fix. I didn't find out why until today.
Posted: Thu Dec 06, 2007 6:47 pm
by TheCatt
Didn't know u still played?
Posted: Thu Dec 06, 2007 6:50 pm
by TPRJones
I started up again a couple of weeks ago. It's fun again, although it probably won't last much longer.
Posted: Sat Dec 15, 2007 11:16 am
by GORDON
Posted: Sat Dec 15, 2007 1:40 pm
by Malcolm
Least they tried to explain it. This is worlds better than anything OSI ever said.
Posted: Sat Dec 15, 2007 2:48 pm
by TheCatt
I read that as "we're kinda dumb, lazy, and rush things out."
Posted: Sat Dec 15, 2007 2:56 pm
by Malcolm
TheCatt wrote:I read that as "we're kinda dumb, lazy, and rush things out."
Yeah, it looks like a simple enough construct in the script that it should've been checked.
Posted: Sat Dec 15, 2007 5:43 pm
by TPRJones
Looks like they just got complacent. After awhile the simpler commands (like delete) are things you just assume you know the details of how they are going to work. You should still test it, but sometimes you get complacent.
Now if they had put it in with a leading /, then yeah, that would have been pretty stupid.
Edited By TPRJones on 1197758632
Posted: Sat Dec 15, 2007 6:11 pm
by Malcolm
Software Q&A folk should be naturally suspicious of any code.
Edited By Malcolm on 1197760346
Posted: Sat Dec 15, 2007 10:51 pm
by Vince
Why doesn't Windows protect its system startup files? That's a good question, one that I have asked myself in these last few days and wish I knew the answer. But of course I'm not going to blame Microsoft for our mistake. Windows doesn't protect those files and therefore software developers must take care not to touch them. We should have been more careful.
Kudos to the guy on that one. Especially since it's so trendy to blame poor programming practices from software vendors on Microsoft now days.