Re: dos functions behave differently under windows XP

From: Jim Carlock (anonymous_at_127.0.0.1)
Date: 06/17/04 

Date: Thu, 17 Jun 2004 04:39:30 +0000 (UTC)

"Tim Roberts" wrote:
> Are you joking??? There has never been a Windows 98 machine
> that could go a month without rebooting. 48 hours was an
> outstanding record.

:-)

Well, I'm telling you I had a Win98 machine that ran a year without
rebooting. Perhaps it was because I didn't play around with unknown
software, perhaps it was because I wasn't doing as much development
as I am doing now. I found Win98 very very stable, unless I was
playing with buggy software, ie buggy software meaning software in
which the crash could be duplicated over and over by the same set
of events (and there was some of that software around).

XP crashes a couple times a month on me ( and maybe it is buggy
software that does it, but currently it's all Microsoft software and they
are bugs that Microsoft conveniently supplies ). And the plug and
play software that comes with XP is specifically what I was refering
to, because buggy software will crash any system, even Win NT.

And continuing on, I'll give you some examples of the XP bugs...

Specifically, refering to the Plug and Play stuff, and the hardware
configuration within XP...

Windows 98, you could go into the device manager and delete a
network adapter and reinstall the network adapter to correct
problems. You can't do that with Windows XP. Windows XP
tends to call a newly detected network adapter as Network
Adapter #2, or #3, or #4. Windows 98 NEVER had that problem.

Also, another example... hooking up a camera to a USB port,
Windows 98 would ALWAYS refer to the camera by its name.

Windows XP on the other hand refers to the NEW device as:

Camera the first time.
Camera #2 the second time.
Camera #2 the third time
Camera #2 the fourth time.
Camera #3 the fifth time.
Camera #3 the sixth time.

Mine is currently up to Camera #5 after about 10 seperate hookups.
The network adapters are up to Network Adapter #6, and that's after
deleting the device from the Device Manager.

And this happens even though it's hooked up to the SAME darn
USB port.

These are XP bugs. They did NOT exist or could be remedied in
Windows 98.

Hope that helps. Don't blindly follow any path because you might
turn left when a canal was dug and now the path turns right. 

-- 
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.

Relevant Pages

  • Re: Cant get Windows XP SP3 to recognise my Canon SX120 IS digita
    ... Nothing odd in Device Manager, but I did find the camera, along with the ... "Windows cannot start this hardware device because its configuration ... "Julia Hopkins" wrote: ...
    (microsoft.public.windowsxp.general)
  • Re: Power supplies in parallel for more current/same voltage?
    ... Windows will not crash NT based operating systems. ... camera, USB port, and Windows 2000. ...
    (sci.electronics.misc)
  • Re: Parallel Device (Problem code 28). What is this?
    ... Explanation of error codes generated by Device Manager in Microsoft Windows ... > but her camera has never been hooked up to this computer yet. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Wake up PCs via RWW
    ... There is a setting in windows that MAY need to be enabled. ... allow the computer to wake up if they are in stand-by/suspend mode. ... Go to Device Manager, right click on the network adapter. ...
    (microsoft.public.windows.server.sbs)
  • Re: OT - Windows & Blows, so far
    ... I just got my nice new lightweight laptop, and it has Windows 7 Premium ... include the "Camera and Scanner Wizard" that came with XP. ... Wizard you are shown thumbnails of the pictures on your camera ... so that you can select the ones that you want to download. ...
    (rec.arts.mystery)