Subject:
|
Re: OS Stability concerns
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Tue, 13 May 2003 01:56:49 GMT
|
Original-From:
|
Rob Limbaugh <rlimbaugh@greenfieldgroup.comSPAMLESS>
|
Viewed:
|
996 times
|
| |
| |
So, someone told your company they had to buy a new car because someone
parked in your space?
Off the top of my head, I'd say the problem was caused by the way the driver
was configured on the ME machines, not because of ME itself---a device
control contention. I'd have to know more details: NT version? Service
Pack level? printer make/model? printer connected via TCP/IP or via parallel
port? printer connected via mini-print server (parallel-to-tcp/ip device)?
Depending on what the equipment is, I could probably model it (I love sick
learning experiences such as this...)
What I can tell you right now is that your company was ripped off. Two
Win98SE's would have been less than $200.
And, for the record, shady tech shops frequently state the way to solve a
problem is to upgrade something. You know how much it costs to actually
hire people that know something?
----- Original Message -----
From: "Purple Dave" <purpledave@maskofdestiny.com>
To: <lego-robotics@crynwr.com>
Sent: Monday, May 12, 2003 8:59 PM
Subject: Re: OS Stability concerns (from/was RE: Vision Command)
> In lugnet.robotics, "Rob Limbaugh" <RLimbaugh@greenfieldgroup.com> writes:
> > Fact is, it doesn't matter what type of computer someone has or the OS
> > on it if hardware and associated resources are not configured properly
> > or if hardware is faulty. I've yet to fix a computer where the problem
> > could be attributed to a "bad OS".
>
> Yeah? Aside from saying the words "Floating Point Math", here's an odd
> problem for you (and one of the primary reasons we upgraded from ME to XP on
> those two machines). Our office had one server/computer running NT, and a
> network consisting of six other computers (two running ME and four running
> 98SE), and a printer networked from the NT server. We discovered that all
> of the 98SE machines had dedicated pathways to the printer, while the two ME
> machines did not. The problem that we had here was that after the server
> was rebooted, if either of the ME users printed to the group printer before
> _all_ of the 98SE machines had printed, the ME machines could randomly grab
> one of the dedicated 98SE printer connections, thereby locking that computer
> off from the printer until we rebooted the server (which then required
> rebooting all of the other networked computers, and was getting to be a bit
> tiresome). We checked with more than one computer consulting firm, and none
> of them was able to tell us how to _fix_ the ME problem. The only solution
> we were ever presented with was upgrading from ME to XP (it should be noted
> that none of these consultants were expecting to actually sell copies of XP
> to us, so it wasn't a cheap way to weasel into a sale). It can't change the
> fact that we've paid for two copies of XP already, but I'd like to know if
> there is a solution that we could have used before.
>
> And I still think it's pointlessly stupid that a straight-off-the-shelf
> computer, running the factory-original OS on the factory-original settings
> can constantly run out of enough memory to shut down on a regular basis.
>
> Regardless, if the OS is never the problem, that makes it even less
> likely that I'll switch from one that has a 64MB minimum to one that has a
> 256MB minimum. I'd rather not let the OS chew up that amount of system
> resources if I've got a slimmer alternative.
|
|
Message is in Reply To:
| | Re: OS Stability concerns (from/was RE: Vision Command)
|
| (...) Yeah? Aside from saying the words "Floating Point Math", here's an odd problem for you (and one of the primary reasons we upgraded from ME to XP on those two machines). Our office had one server/computer running NT, and a network consisting of (...) (22 years ago, 13-May-03, to lugnet.robotics)
|
10 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
Active threads in Robotics
|
|
|
|