Welcome, Guest. Please login or register.

Author Topic: A common attitude with Windows users here  (Read 20690 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Waccoon

  • Hero Member
  • *****
  • Join Date: Apr 2002
  • Posts: 1057
    • Show all replies
Re: A common attitude with Windows users here
« on: November 03, 2003, 12:03:43 AM »
Quote
Mikeymike:  You'll complain to the ends of the earth how slow/rubbish/unstable/whatever your WIndows installation is, but you are unwilling to do anything about it, eg. find out how to configure Windows correctly.

That would be easier if Windows didn't ignore or discard your changes from time to time.  Ever try to use the "View:  Like current folder?"  It usually takes a restart before it actually starts viewing like the current folder, and a lot of times Windows just "forgets".  Every time I re-install Windows, it takes 3-4 days before Windows "learns" how I want it to be configured.  I suppose if I went into RegEdit, I could force it to learn faster, but hey...

It would also be nice if Microsoft didn't change everything all the time.  Most people don't want to spend days re-learning everything just because of a critical update.  Microsoft changed their driver wizard in Win98 a while ago, and now a lot of Win98 drivers don't work anymore, saying that the drivers are not designed for your hardware.  I've had a lot of customers return hardware because of that, and from personal experience with my own Win98 machine, I know it is NOT their fault.  It's because Microsoft is still innovating a product that has a set methodology and SHOULDN'T change.  But if they didn't, IE6 and other newer MS products may not work.  Between IE and older drivers, guess which product won?

Quote
Willing to whinge, unwilling to learn. That's what I think it comes down to.

For home users, perhaps, but it's worth pointing out that the people who buy software for business purposes are RARELY the people who actually use the software.  My boss spends tens of thousands of dollars on software I tell him NOT to buy, and all the resulting problems are my responsibility.

BTW, I am no longer working there, and am looking for a new job.  I certainly won't work anywhere that used that same crap software, that's for sure.

Quote
KennyR:  When I buy a car, I expect it to run with zero maintainance. If I have to spend every weekend fixing it or pushing it in the mornings, it's time to buy a new car.

I've used that same analogy when desribing the "professional" machines I use at work.  Our Kodak DLS printer has a problem just about every week, and when a technician comes in to "fix" the problem, there's really nothing they can do.  That's why they charge $10,000 a year for maintenance contracts.  If we hadn't bought it, we would be up to over $60K in repair bills by now, and the machine is only two years old.

Meanwhile, my old car, a Saturn, worked flawlessly for 3 years with only oil changes, chassis inspections, and new brakes.  Compare that to the awful BMW iDrive machine, which was almost completely software controlled, and in some cases the engine wouldn't even turn off because the car couldn't tell if the magnetic key was removed or not.  I think it had to be totally recalled, but I haven't followed up on that.

Quote
As a professional developer, I can honestly say that its "always the user"!

If you're a good programmer with lots of experience with UI design, than I would agree.  This does not reflect the industry standard.  One product I use at work refused to download new photo orders from the company's server.  It gave no error, it just said "no new orders".  After playing phone tag for a couple days, I got to talk to the lead programmer, and he said I should delete half the orders in the order archive and try again.  He said it like it was the most obvious thing in the world.  Since the software automatically deletes orders after one month, or if your computer is out of disk space, I never would have thought that manual maintenance is required, especially since we DON'T want to delete the order archive.  We also had plenty of disk space.  I should repeat that the software gave no error, and the programmer treated me like I should have known better.

It's not always the user's fault.  Nobody is right all the time, especially the people who write the software I use at work.  Unfortunately, most low-volume, "professional" software companies seem to operate like this.  So long as the bosses buy the software (and never use it, themselves), the problems just keep getting worse.

Quote
Oh, of course its the users fault, we just love editing the windows registry, removing ad-ware and spy-ware, defragging, devirusing, streamlining the startup, dealing with IRQ's and hardware conflicts, all from a noisy arsed box. Why should I go back to Amiga?

Well said.  Maybe if Microsoft didn't make so many "hidden" parts of the registry that allow spammers to wedge in things that don't show up in MSConfig and TweakUI, we wouldn't have so many spy-ware problems.  Viruses I'm not too sure about.  I have my Active-X controls set to "prompt" and haven't had a virus in years.  Then again, how many people know what an Active-X control is?  What starter book will tell you that right-off without bombarding you with 400 pages of fluff about how wonderful Microsoft is?

Quote
Methuselas:  I'll give credit, where credit is due. 2kPro kicks @$$. I haven't had a LICK of problems with it in my two years of use. Most of my installs were 'cos of replacement HDDs (NEVER BUY Western Digital. I have replaced 3 REFURBISHED drives, all sent to me as replacement to a NEW one still under warranty!!!).

Win2K is great.  My dad's XP system drives me nuts and I refuse to upgrade.  All I do is Photoshop and e-mail, anyway.

I have to contest your advice about WD.  I will *ONLY* buy Western Digital.  I bought three Maxtor drives and all three went belly up within 6 months.  They were all replaced with refurbished drives (every company I know does that).  I've also seen 2 IBM drives give up the ghost, as well as a Fujitsu and Samsung.  I've personally owned 4 WD drives and never had a problem.

HD's are the least reliable component in your PC.  All drive manufacturers have their issues.  The only thing you can do is make backups.  I have at least 2 full backups of my system at all times, and keep them up to date within 2-3 weeks.  I keep daily backups of work in progress and haven't lost anything in... years, I think.

Quote
Mikeymike:  I would say 50% of the time that's down to cheapo hardware, 25% of the time users that don't know how to configure it and/or Windows and 25% the fault of MS and hardware vendors in driver writing.

Sounds fair.  Every time someone asks me to fix their computer, they have some cheapo motherboard where drivers are just NOT available.  That usually means re-installation is impossible, or something to sweat over.   ;-)

Quote
PPCRulez:  And DLL/registry hell is not very user-friendly.

I've always felt that DLL hell is largely the fault of developers.  DLLs should be local to the application folder, and you should check version numbers, first.  I've never run into DLL hell except for a few oddball apps under NT4, and a wealth of idioticly programmed freeware apps.  Ever recall having to download Allegro libraries or "Glut32.dll" to get something to work?  Morons.

Mikeymike is right.  DLL hell is a thing of the past.

Quote
Mikeymike:  I've never seen NTx just "give up the ghost" and die

I have.  To be fair, I think it was because of bad SCSI drivers, but that's not my problem.

Attempting data recovery from an unbootable NTFS partition is hell.  NT4 doesn't have a recovery console, Win2K won't let you access any files because you don't have permission, and re-installing Windows on top of itself makes several duplicates of your user profiles, which you can't remove unless you do it from the registry (the GUI tool won't list the profiles, but the system still writes files to them).  There is a way to change the security permissions so you can read files from the Recovery Console, but I never got it to work.  It still tells me Permission Denied, even when I log into the admin account.  Windows security is very weird.  The only thing worse is Windows networking.

Lesson learned:  always use FAT for your boot partition and NTFS for other partitions, 'cause if the boot partition dies, you might have to transfer the HD to another machine to read your files on C:.

Quote
If the car was obviously badly designed, I would be justified in this view, don't you think?

Yes.  Bad quality is less tolerated in the automotive market, and competition is much more fierce.  Then again, you don't have to worry about "special" gas formulated just for your car, or get service from just one machanic in the country.

Quote
PPCRulez:  Yes, that is what happened. I just pressed the reset button after a complete system freeze due to the keyboard dying. After that it wouldn't boot, in fact I couldn't even get to the Safe-mode.

Oh, I've seen that plenty of times when plugging in USB card readers.  Windows automatically reassigns the drive letters, and... POOF... even safe mode doesn't work.

USB card readers are the work of the devil.  I can't tell you how many customers bring them back, and *I* can't get them to work, either.  Very, very bad manufacturer support, that's what!
 

Offline Waccoon

  • Hero Member
  • *****
  • Join Date: Apr 2002
  • Posts: 1057
    • Show all replies
Re: A common attitude with Windows users here
« Reply #1 on: November 03, 2003, 08:34:45 PM »
@PPCRulez:

Oh, boy...  I've seen this problem way too many times.  Windows is VERY fussy about the order in which you attach hardware to the machine.  Some devices, like my Epson scanner, require you to boot up the computer with the scanner unattached or turned off, and THEN attach or turn on the scanner.  If the scanner is on while the system is booting, the TWAIN driver says the scanner can't be found.  I have an HP printer which is a real pain to install.  The driver must be installed first with the printer unattached.  If you plug in the printer before installing the driver, it will COMPLETELY mess up your machine, and you'll have to delete lots of USB entries in the device manager just to clean house so you can try again.  Once the driver is installing, you'll have to plug in the printer ONLY when it tells you to, so it can autodetect it.  Sometimes it works, and sometimes it doesn't.  It took me a few hours just to install the driver the first time I bought it.  If it wasn't such a damn good printer, I would've brought it back!

Try this:
- With the device plugged into your usual USB port, open the Device Manager.  Find the entry for the camera and remove it.  Unplug the camera, and THEN click Scan for Hardware Changes.  Do not click Properties and try to Reinstall Driver.  That hardly ever works with USB devices in my experience, even though it works with everything else.

- At this point, you're at the mercy of the driver.  Sometimes you have to install the driver first, sometimes after.  Sometimes you have to have the camera plugged in before the computer starts, sometimes after.  I have a feeling that since the OS recognizes the camera as a Mass Storage Device (which it shouldn't), you might have to install the driver first, then plug in the camera.  Scanners, printers, and cameras usually don't install by plugging in the device first, and then getting a prompt for the driver.  Card readers, USB drives, and low-speed devices usually WILL install this way.  You'll have to experiment.

- See if your manufacturer has a more recent driver for downloading.  Some downloaded drivers are more basic than the ones you get on CD-ROM, EVEN if they are the same version number!  Downloaded drivers may have updated directions on what order to do things.  Manufacturers tend to change their mind about installation all the time.

Also keep in mind that high-speed USB devices like scaners and digital cameras (unlike mice, keyboards, and joysticks), probably have to be plugged into a root USB port, and must always be put into the SAME port every time you use it.  If you swap ports, you'll have to re-install the driver for each USB port, and if you use a USB hub, chances are you'll have communication problems, or the device will not work at all.  When I have my scanner plugged into a hub, it will scan 25-40% of an image an then freeze.  In a root port is works flawlessly.  Only the three fingered salute will shut down the TWAIN driver when it freezes.

Microsoft's USB standard absolutely sucks.  Many manufactuerers try to "fix" it by doing strange stuff with their drivers, and that just seems to make the problem worse.  My HP printer is the hallmark of horrible, horrible driver design (it also installs junkware, like a desktop folder that will automatically upload pictures to HP's server for sharing to family members.  You have to explicitly delete it AFTER it's been installed.  Lovely).
 

Offline Waccoon

  • Hero Member
  • *****
  • Join Date: Apr 2002
  • Posts: 1057
    • Show all replies
Re: A common attitude with Windows users here
« Reply #2 on: November 04, 2003, 06:08:16 AM »
Quote
PPCRulez:  You don't have to (nor can) install any drivers.

Oh, those are bad.  Lots of the card readers we have at work don't have drivers, or even directions!  Just plug it in and it works!  Yeah, right.  I suppose that's why 5 out of the 6 Unity Digital USB readers we sold were returned to us.  I plugged mine into a Win98 box, and it kept asking for a driver.

For that kind of device, though, you'll have to clean out the device manager, and then plug it in AFTER the computer starts.  Also, if you get it working, type "diskmgmt.msc" in the Start Menu/Run dialog, make sure a card is in the camera, right-click on the mass storage device, and click Change Drive Letter and Path.  Without a dedicated, assigned drive letter, the device may appear and disappear for no reason.  Make sure there's a card in the camera when you do this, or Disk Management will throw a tantrum (removable disks tend to do that).

Quote
fx: linux structure of files is a mess

I agree.  I think it's a bit hypocritical of UN*X people to criticize Microsoft for dumping everything in the System folder.  They do the same thing with the "bin" folder.  Also, there's so much stuff that just goes in the "etc" folder.  If you're suddenly stuck having to edit your congig files by hand (and that will happen), digging through the "etc" can be a real pain, especially from a vanilla console that doesn't use color (unless you know how to turn it on).  Everything is case sensitive, too.  It took me a while to figure out why "xconfigurator" didn't work, but "XConfigurator" did.  God, I hate that.

I know standard I/O and pipes are useful for programming, but this is the 21st century.  Why are we still bumming around with Telnet-compatible B&W shells?  I miss the old text user-interfaces (TUIs) used in MS-DOS.  Navigating interfaces without a mouse ROCKS.

Quote
And about the "having to reinstall the OS" problems, this has never happened to me in any OS except Windows, I usually reinstall Linux every now and then because it's grows huge with programs I'm installing and testing, but Windows has actually crashed on me once and showed a message telling me I had to reinstall windows.

Ah, the dreaded registry corruption.  I've only seen that happen under Win95, though.  Win2K only seems to blow up when I put on new drivers or something goes wrong with WindowsUpdate.

I haven't re-installed my A1200's HD since I ran into a filesystem mishap in 1995.   ;-)

Quote
Hammer:  The reason for that is simple i.e. Windows 9X's VXD drivers doesn’t work with Windows NT5.x style driver modelling.

Simple reason, but inexcusable.  Just because Microsoft tidied up the driver installation GUI doesn't mean you shouldn't be able to use Win98 drivers in Win98.

Quote
One could have another cut-down installation of WinXP/Win2K to rescue the main boot drive.

What a waste of 1 gig!   :-)

Quote
No one has forced you to upgrade to Win2K/XP IF Windows 98 does the work for you.

Wait, do you think I'm complaining that Win98 drivers don't work in Win2K?  Of course they won't.  I mean Win98 drivers won't work in Win98 because IE6 includes a new driver installation system that isn't fully compatible with older drivers (and can't be removed once installed).

I could care less since Win2K is far supirior, but my customers keep returning merchandise because it doesn't work on their computers.  When I try it on a Win98 box I have lying around, I find out those products won't work on my machine, either, if I have IE6 installed.  Companies shouldn't be forced to update their drivers regularly because Microsoft wants to screw around.

Quote
the_leander:  I do find that a lot of the problems I've encountered is due to hardware not sticking to the standards, usb stuff especially seems to be bad for this.

I've found it's because of drivers, politics, and idiotic marketing decisions, not the hardware.  USB is really good, IMO, it's the Windows USB driver model, and many manufacturers' rediculous hacks, that really suck.

Quote
ronybeck:  As a result MS Word took 10-15 minutes to open a document because it kept trying to poll the printer server.

Isn't it amazing how long it takes Windows to realize that something isn't actually there?  Netscape running on a Mac does the same thing.  The Internet connection is down, but it will keep trying to load a webpage for 15 minutes, all the while the "Stop" button is grayed out!  Doing graphic design work on the PowerMac was a horrible experience.  Everything locked up the system for minutes at a time, before it realized that the device didn't exist!

Quote
No major qualms, I just like the concept behind the AmigaOS a lot more.

Most people have no major qualms with Windows, until something goes wrong.  Windows is so inconsistent, that one person may have a nightmare on his hand, while other people just sit around in bewilderment, giving helpful advice, like, "I've NEVER had a problem with MY computer!"

Good for you!

Quote
I've never used Win2K really, maybe I'm missing out on something here...

A faster, lighter XP without the eye candy, no stupid product activation, and lesser game compatibility.  Everything today runs fine under Win2K, so I have no reason to upgrade to XP.  Also, I change my hardware a lot, so XP's anti-piracy nagging would get on my nerves.
 

Offline Waccoon

  • Hero Member
  • *****
  • Join Date: Apr 2002
  • Posts: 1057
    • Show all replies
Re: A common attitude with Windows users here
« Reply #3 on: November 04, 2003, 06:39:42 AM »
Quote
melot:  All the computer manufactures advertise their product to the general public as the
greatest thing since sliced bread, and
subconsiously we beleave the ads.

Don't all companies do that?  A company is nothing without its reputation.

These days, it's not called reputation.  It's called "brand awareness".

Quote
People need to really
pay attention to the ads, you know like 24/7
tech support. Why do they need that if the
software worked as advertised.

So, if they offered 8/5 tech support, you'd be more interested in their product?   :-)

What really needs to happen is people need to get away from the hype and think about what they really need.  I use Photoshop all day, so I need a top-flight system.  If all I did was browse the web, a celeron would do me fine.  My dad's friend, on the other hand, spent $4,000 on a 3+ Ghz P4 with dual 250 Gig hard drives!  He doesn't do any business work on his system, so what does he need all that power and storage for?!  If he wanted it for a game machine, he could get a better long-term deal by upgrading his machine later, rather than getting an end-all upgrade now for that much cash.  I don't get it.

Another hype item:  digital cameras.  I can't tell you how many people walk into my [ex]-store wanting to buy a digital camera, but they have no clue how much time and money they'll have to invest.  GO DIGITAL is the war cry in the photo industry, because it's the way of the future!  Apparently, the way of the future involves not being able to print pictures off a memory card, because a Kodak DLS printer can't read JPEG files with certain kinds of meta data.  I find it very amusing that digital photos taken with a Kodak camera may not come up on a Kodak DLS minilab, and in some cases, may actually crash the workstaion.  I really hated that machine, and I'm glad I'm not working at that store, anymore.

I'd like to say that's a Kodak issue, but apparently, all manufacturers are having these kinds of issues.  Instead of making good, solid standards, they just abstract everything with XML, DPOF, KIAS... and then require you to install all the "client" programs to work with thier crappy little applets.  Kodak is run by script kiddies, and Fuji, Agfa, Polaroid, Noritsu, and all the others, aren't much better.

I mean, there isn't even a standard way of numbering digital photos as you take them.  The customer orders frame #142, and they get DCM00142.JPG, which is not the same thing.  Many camera manufacturers haven't even agreed whether movie files should be counted as frame numbers or skipped entirely, making it near impossible to order prints from a memory card if there's movies on it.

The point:  This is the information age, but nobody is concerned about the QUALITY of that information.  It's just a war over volume, like it has been in the computer industry for 20 years.

Quote
I respect and envy Mikey's knowledge.....
If I could just figure out where to even start
on the Damned thing I would probably be OK.

Another think I wish more developers realized, is that while we all have the ability to learn about our computers, there are many things people shouldn't have to learn.  What's the point of spending $300 for an operating system, just so you have to spend weeks learning how to use it?  Why do people get all pissy at newbies because they don't know, "oh, of course you're having trouble, because you didn't disable *THAT* problematic feature!"

Time is money.  If people feel like wasting hours of their life to figure out one little gadget, they should stick to freeware.  Commercial developers have an obligation to make software that meets the customer's expectations.  If your users can't use your software, that's your own damn fault, not the users.