WTF!?! - "DATA IS INVALID" installing device driver????
Bob
both motherboards work GREAT with win98 - all devices work.
BUT UNDER WINDOWS 2000 - I CAN'T LOAD A SINGLE DEVICE DRIVER WITHOUT
GETTING:
"An error occurred during the installation of the device
The data is invalid"
THE DATA IS INVALID!?!?!?!? - WTF DOES THAT MEAN????
THE DATA IS NOT INVALID - WIN2K IS!! - these drivers work fine under
another OS!!!!
does anybody have a frigging clue what windows' problem is, or why I
would get this ridiculus error message that tells me NOTHING?????
this seems to be a problem with ALL ON MOTHERBOARD devices - when I
was running the KR7a-133, that meant no usb - which I accepted and
dropped the issue.
but now with the max2 having just about EVERYTHING on motherboard - I
NEED A LAN adapter that works!!! (not to mention usb too!!)
I've searched MS knowledgebase, and found it to be completely USELESS!
any help would be appreciated!
tia - Bob
Bob
the drivers for windows 98 work fine under 98; the drivers for win2k
cause the "data is invalid" error. - Since the SAME company generated
both sets of drivers - I believe I can safely assume that the win2k
drivers SHOULD AT LEAST INSTALL before failing!!!
Bob :)
On Fri, 14 Mar 2003 08:21:30 -0500, nosp...@will-enterprises.com>
wrote:
>Gee, if the drivers work fine for another O/S, it seems they're probably NOT W2K
>drivers! :-)
Tony Hwang
First of all, if you downloaded it, it could have errors incurred during
DL. If you OC your system, it can cause it as well.
If you unzipped it, it could have an error. All of above is known to
happen. How stable is your system? For an example can you run memtest86
error free over night?
Tony
Void_Singularity
W2K, unlike Win9x, enforces registry security. This is usually caused by
trying to install a driver without administrative priviledges (a definite
no-no in W2K) or by an installation script that is improperly written by
hardware manufacturer.
example:
http://www.staudio.de/kb/english/datainvalid/
"Bob" <nospa...@starnetwx.net> wrote in message
news:pjk37vkmf9parukmn...@4ax.com...
Bob
thank you very much for your response....
in answer to your Q's; the system is rock solid; brand new MB; I
burned in w/ memtest86 with no problems. the installation of win2k is
brand new also - so there isn't any crap sitting around from other
apps... basically the whole system is virgin top to bottom.
other ideas? :)
tia - Bob
Bob
sorry - I forgot to tell you that I've tried drivers both from the
original driver cd, as well as freshly downloaded...
when I loaded win98 onto another hard drive in the same box;
everything worked perfectly. - problem isn't the drivers - it's
DEFINITELY win2k.... (yes, I suppose you could argue that the win98
drivers were ok, and the win2k drivers were bad - but that's really
stretching it IMHO - besides even if they were bad, the freshly DL'd
1's should have resolved that - and the error for all attempts was
identical - AND remember - SAME ERROR across multiple devices!!! - so
I rule out the drivers altogether)
Bob
On Sat, 15 Mar 2003 01:15:58 GMT, Tony Hwang <drag...@shaw.ca> wrote:
Bob
appreciate your response;
I am aware of admin privledge related issues; and for ALL attempts, I
was signed on as admin; (in fact I don't think I even got around to
setting up any other user accounts yet)
I am aware of the "fix" that is displayed at the URL you gave me;
however I don't believe that the average user should have to make
registry permission changes to install device drivers ESPECIALLY when
they are signed on as administrator!!!
so while the registry "fix" you refer to does allow ME to workaround
the problem; there is NO WAY I will pass out that information to my
users....
there MUST be another solution to the problem - that's what I'm really
looking for - and what REALLY ticks me off is that MS doesn't have ANY
information about this in their KB.
anyway - don't mean to bend your ear - guess I'm venting!
tx again for your help - I'd appreciate any other ideas/solutions you
may be aware of!!
Bob
Bob
I can certainly understand the position you're taking, and I believe I
understand how I might appear biased, and without logic.
however; let me restate some of the facts, and ask if you would come
to a differing conclusion, or if you would be so kind as to point out
a flaw or hole in my logic. ( I would be most appreciative )
1) the "invalid data" error is reported on various forums, and
websites (although not MS); so while the majority of people may not be
seeing this problem, there certainly is a group that does. (what this
group has in common I have no idea)
2) I personally have seen the problem exhibit on 3 different
motherboards; 2 different models from Abit, 1 from Asus. I grant you
that all motherboards I've tried did use VIA chipset; so I suppose you
could argue the problem is with them. However to the best of my
knowledge - the chipset has NOTHING to do with the OS validating or
accepting a device's software driver.
3) The problem has presented with drivers used from original
distribution CD, as well as with varying versions downloaded with
newer version #'s.
4) If I alter the registery permissions, ALL versions of the drivers
install without problems, AND function perfectly. - This at least
proves there's NOTHING wrong with the drivers. - So you could argue
the Mfg of the driver has a poor installation - Not true - I tried
installing the drivers thru windows without using the Mfg install
script. (this also proves the MB chipset has nothing to do with the
issue)
5) the issue appears to only appear under win2k (and XP from what I've
read) - win98 has NEVER shown this problem. - I even tried installing
linux just for S&G's; and IT WORKED FINE!
So - in conclusion - my logic follows thus:
#1 proves that I'm not alone with this problem (maybe in a minority),
but the problem clearly exists.
#2 proves that the problem is not limited to a single motherboard Mfg
or model.
#3 & #4 prove the problem is NOT the drivers.
#5 proves the problem is clearly a microsoft windows 2k/xp issue
I have no ego problems, and would LOVE to be shown that I am somehow
wrong - I only ask that my fault is pointed out, that I may learn from
it. However, I can see no flaw in my logic, and believe the facts
clearly dictate the problem is with microsoft win2k(xp).
I eagerly await any rebuttals! :)
-Bob
On Wed, 19 Mar 2003 08:04:17 -0500, nosp...@will-enterprises.com>
wrote:
>Now, let's think about this. Millions of people use W2K, but it's fatally
>flawed because you have a specific configuration that fails. And, the hardware
>can't possibly be at fault, through a logical process that I can't fathom.
>FWIW, as long as you continue to blindly blame W2K for your troubles, you'll
>probably still have the troubles. When you adopt an open mind and try to
>actually diagnose the problem, you may make progress.
>
>I really can't believe I'm actually defending Microsoft here, but you're barking
>up the wrong tree!
neal wilson
> so while the registry "fix" you refer to does allow ME to workaround
> the problem; there is NO WAY I will pass out that information to my
> users....
would you expect your users to be installing their own machines anyway?
Christ...I can just imagine some of our users having to do
that...hahahahahahahahahahahaha Think the company would quickly revert back
to pen and paper! Now there's a thought. Sure would make my life a lot
simpler!
Zilla
--
- Zilla
(Remove XSPAM)
"Bob" <nospa...@starnetwx.net> wrote in message
news:lmaf7vc987923ejom...@4ax.com...
Bob
to try...
although - since I've tried it with 3 different motherboards, I
consider THAT the same as trying 3 different pc's.....
Bob
Bob
admitedly, it's not often a user would install such a driver - however
- I have the same problem when installing an application such as
Laplink - which DOES install it's own drivers...
applications such as this, is more common for my users to install;
many have admin rights to their own pc's....
(this is a liberal group)
Bob
hardware (minus the motherboard) prior to having the previous
motherboard blow up.
this problem appeared BOTH on the previous installation of win2k ( the
same hard drive from the blown MB ) AND a VIRGIN installation on a new
hard drive. (from the ONLY installation CD I have.) I SUPPOSE you'll
argue that my installation cd has gone bad? - If so, then why does
everything work if I go into the registry?
I believe that I've conclusively proven the driver's are in perfect
working condition. (based on prior post)
Further - I'm NOT the only one complaining about this problem - I'm
apparently just the only one who wants to see a resolution to the
problem WITHOUT manually forcing changes in the system registry!!!
(nospam)ng - I must assume that from the lack of assault on my logic,
that you can find no fault. So - I would offer to you this: Just
because the majority of users don't experience a certain problem
DOESN'T mean that problem doesn't exist!!!!
(exuse the double negative)
This problem IS REAL - albeit seen by a minority - the problem IS
CLEARLY a microsoft issue. One that because only a minority have
experienced, that microsoft must not see as a priority to address.
On Fri, 21 Mar 2003 07:50:41 -0500, nosp...@will-enterprises.com>
wrote:
>Not really the same. If you have something corrupted in your W2K installation
>or installation media that is causing the problem, it's still there with another
>MB. Unless the drivers themselves are corrupt, it's pretty hard to imagine that
>you're the only person complaining about this issue.
Bob
I can tell you that on another win2k machine (actually another
motherboard) that the EXACT same problem exists - using different
drivers (drivers specifically for that motherboard)
This IS essentially another pc - I've since replaced EVERY component
of the box (except the cd-rom, and floppy).
On Thu, 20 Mar 2003 16:03:39 -0500, "Zilla"
<zilla6...@bellsouth.net> wrote: