All Things Microsoft > Microsoft Software
Windows at fault - again
psyjax:
None the less, should the setup program be such a timebomb waiting to happen? I mean seriously, what if this happens by accident. The program should at least be aware enugh of whats going on around it to give you a proper warning and istructions and not take down your entire system because you missed a note in the dialogue or absentmindedly left a disk in. In the long run I think this is M$'s fault.
Centurian:
Hey,
quote:Originally posted by psyjax:
None the less, should the setup program be such a timebomb waiting to happen? I mean seriously, what if this happens by accident. The program should at least be aware enugh of whats going on around it to give you a proper warning and istructions and not take down your entire system because you missed a note in the dialogue or absentmindedly left a disk in. In the long run I think this is M$'s fault.
--- End quote ---
Ok maybe I am crazy. There are alot of things wrong with windows. IMHO this isn't one of them. I see it as a simple case of Read The Documentation.
In so far as that goes I could say the same is true about Mandrake because the docs tell you things you need to do prior to installing. If you don't know those things (because you did not read the docs) Mandrake can be much more difficult to install also. Whether it is a screen prompt or an online manual or a book people should take the time to read the docs that come with an OS.
psyjax:
I don't disagree with you at all, I'm just saying, it wouldent be too hard for M$ to put in a line of code or two that check the disk drive and say "you have a disk in, this may cause problems, please eject it" that's all. I mean, it's not like he was pouring coffee on the circuit board, it was a disk in the drive, that shouldent be a big deal to begin with at all.
Whatever, maybe I'm just picky, but I think this problem could have been avoided with a little forsight from the programmers.
For example, when you run an Installer App in OS X or in other Mac OS's it says you can't have other programms running while it installs. If you try to install and another program is running the installer warns you and asks if you want to quit the running program or stop the installer. This is standard on even the system install.
[ March 18, 2002: Message edited by: psyjax ]
[ March 18, 2002: Message edited by: psyjax ]
Centurian:
Hey,
quote:Originally posted by psyjax:
I don't disagree with you at all, I'm just saying, it wouldent be too hard for M$ to put in a line of code or two that check the disk drive and say "you have a disk in, this may cause problems, please eject it" that's all. I mean, it's not like he was pouring coffee on the circuit board, it was a disk in the drive, that shouldent be a big deal to begin with at all.
Whatever, maybe I'm just picky, but I think this problem could have been avoided with a little forsight from the programmers.
--- End quote ---
I can see your point here but think about it. Windows does not know how you booted your system. It could have been from a boot disk or from Dos on your hard drive. I suppose it could even have been from a different CD prior to putting the Windows CD in. Also Windows does not know the boot order you have setup in your bios. Your system could boot directly to the hard disk even though there is a floppie and a CD in the respective drives. So sure they could put in some code to check for a floppie but in reality most people are booting from a hard disk with an earlier version of windows or dos already installed. So the screen docs is a warning. Now suppose you keep a floppie in your a: drive constantly and keep your bios set to boot directly from C: drive. ( I actually know one person who does that ) In that case windows would not reboot until the floppie was pulled. Of course that would upset some people also. So either way someone will be upset. I think they did what should have been done in that particular situation.
quote:
For example, when you run an Installer App in OS X or in other Mac OS's it says you can't have other programms running while it installs. If you try to install and another program is running the installer warns you and asks if you want to quit the running program or stop the installer. This is standard on even the system install.
--- End quote ---
Windows does that also for installing Apps but we are talking very different circumstances. I have never used a Mac and have only once seen one run but I have heard that they use only their own hardware. I also would guess that there is only a limited amount of ways you can install the Mac OS. Possibly only one way for all I know. Where as with windows there are many ways that it can be handled. With Windows you can boot from a floppie or Hard disk and install from floppie (yes believe it or not you can still do that) or CD. I used to know a guy that kept a copy of W95 on his third hard disk and would install it from there.
So in this case I think MS did what was appropriate.
psyjax:
Jeez... if your gonna pen an essay I guess I'll conceed :D
Nah, I see your point, it's more of a hardware situation than anything else I would imagine. I have worked with windows machines before even had one back in the day. Little things like this sort of irritated me, I can see their functionality in a practicall sense due to the computers history and userbase, but perhapse not as elegant a solution as I would have liked.
Perhapse Mac's have spoild me since their Hardware and Software are so firmly integrated.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version