Need help manually placing .sys and .vxd files for WUSB54ag

[Flasche]

As my title states I need help manually inserting the files (WUSB54AG.sys, and WUSB54AG.vxd) into their respective folders. (these are files for the hardware not the software) I found that both versions of the wusb54g (wusb54g ,and wusb54ag) had all of their files for windows 9x purposely renamed and moved around the install folder to mess up .exe installer. It doesn't help that after fixing the "folder issue" that windows me (and 98se) after using the windows driver file placer (Prob named it wrong please give the name for it) keeps on stating that the adapter has been installed wrong. The thing is though is that it does work since I did get it to work using windows driver file placer (seriously am I calling it wrong) once after fixing the folder issue. Unfortunately it did brake after installing avast and not doing an immediate restart (downloading flash at the time). So if anyone knows were to place these files can you tell me where. (another reason why to hate Cisco )

[dencorso]

Your request makes no sense at all to me. But that's not required. Unless those files have a path expressely set in the registry (do search it thoroughly), just dropping both filles in %windir%\system should be a safe bet. If that's not enough, leave the .VxD there and move the .sys to %windir%\system32\drivers ... Wait a sec! Are them USB drivers? If so, they simply aren't needed for Win ME. Good luck!

[jaclaz]

Your request makes no sense at all to me. But that's not required.

But it usually helps.

Flasche, try explaining what the problem is, i.e. what is the actual Goal that you want to achieve.

The risk of slipping on a chocolate covered banana is high

http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html

Start with a basic standard litany:

http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html

jaclaz

[submix8c]

? Where did you find a Driver Install that has a VXD? I only see the SYS-file. In/from the Utility Install?

I think I had responded to a similar request about thw Win98 Drivers - I have them here (V1 and v4).

Edited February 11, 2014 by submix8c

[dencorso]

What hardware are those WUSB54AG drivers for, if I may ask?

[submix8c]

My apologies... you named TWO Models. I now see the VXD (in the AG set). Linksys/Cisco only names one "version" as v1 (the hardware version). The INF only has "VID_13b1&PID_000c" listed.

As dencorso said, it would be better to name specifically what you have on the actual hardware .

Edited February 12, 2014 by submix8c

[dencorso]

Once VIDs and PIDs are known, one can even try adding them to the .INF for the .VxD driver, to find out whether it can work with the given hardware or not.

[Flasche]

Sorry for a late reply but I have been busy with school and yet another snowstorm.

But it usually helps.

Flasche, try explaining what the problem is, i.e. what is the actual Goal that you want to achieve.

The risk of slipping on a chocolate covered banana is high

http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html

Start with a basic standard litany:

http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html

jaclaz

Actually everything you stated is true I'm terrible at asking questions, writing, and EXPLAINING. OT My English teacher is always yelling at me for not asking for help, but what makes it so hard to ask is I understand the thing (like a writing assignment) but cant translate it into proper words and syntax which makes really sense and all that gives me a massive headache. Thanks for the Déjà vu. (The way I wrote this probably seems like I'm angry at you but I am not and really glad that you pointed it out and tried to help you really are smart) I hope this clears up everything. If I still don't properly explain I'm really sorry please forgive me

Your request makes no sense at all to me. But that's not required. Unless those files have a path expressely set in the registry (do search it thoroughly), just dropping both filles in %windir%\system should be a safe bet. If that's not enough, leave the .VxD there and move the .sys to %windir%\system32\drivers ... Wait a sec! Are them USB drivers? If so, they simply aren't needed for Win ME. Good luck!

Yes it is a usb network adapter why?

My apologies... you named TWO Models. I now see the VXD (in the AG set). Linksys/Cisco only names one "version" as v1 (the hardware version). The INF only has "VID_13b1&PID_000c" listed.

As dencorso said, it would be better to name specifically what you have on the actual hardware .

As said I did make it quite confusing and I'm sorry

Flasche, try explaining what the problem is, i.e. what is the actual Goal that you want to achieve.

I'll give it another shot. I have been trying to install the WUSB54ag onto my windows me computer. (so I can connect to the internet) The way you are supposed to do it is first install software than plug in adapter, but for me that doesn't work. (I used first setup you see not the setup in utilities *this is initially*) After looking in the drivers folder I noticed that the WUSB54AG.sys was misplaced a folder back. (suspicious maybe ) Though I also noticed that the .vxd and .sys files were the same so I just copied the .vxd and changed the name of the copied one and made it a .sys. (also it was newer than the .sys they gave) I then gave up on the initial exe install and the way you are supposed to install the adapter and decided to try hardware first then software. After a while windows finally said that that the adapter was installed correctly instead of having an issue. And after using the setup in the utility folder the adapter finally worked. Unfortunately It broke a short while later when I installed avast without restart immediately. (when prompt to) Though this let me know it wasn't a software issue. I confirmed it when I installed the software (after uninstalling the adapter) and seeing that it was disabled when the hardware was said to be installed incorrectly but when the hardware was said to be installed correctly it wasn't disabled (obviously). The Linksys WUSB54ag only has one version that I'm are of. So that why I need to know how to manually insert these files. I hope that this explanation was better.

(another reason why to hate Cisco )

OT If you want to know the first reason I can post a video, but the video is long so... ya

[dencorso]

Some (not too much) random thoughts elicited by the reading of your latest post:

1. It's OK to have difficulty at explaining things... as long as one honestly tries to, practice makes perfect and one gets better at it the more one does it.

2. Now, .sys and .VxD are very different animals... renaming a .sys to .VxD or vice-versa, in the very best case, will result in things not working at all...

3. A .VxD for a Mass Storage Device usually goes into %windir%\system\iosubsys, while other types of devices usually leave their .VxD files in %windir%\system, whereas all .sys files go into %windir%\system32\drivers... there are exceptions, of course (and those confirm the rule...).

4. I doubt avast has anything to do with whatever happened, unless it decided to delete and/or quarentine things it should not, as anti-virus applications are prone to do, when run unleashed...

[Flasche]

1. It's OK to have difficulty at explaining things... as long as one honestly tries to, practice makes perfect and one gets better at it the more one does it.

Thanks man

3. A .VxD for a Mass Storage Device usually goes into %windir%\system\iosubsys, while other types of devices usually leave their .VxD files in %windir%\system, whereas all .sys files go into %windir%\system32\drivers... there are exceptions, of course (and those confirm the rule...).

Thanks I'll put them there and see what happens

4. I doubt avast has anything to do with whatever happened, unless it decided to delete and/or quarentine things it should not, as anti-virus applications are prone to do, when run unleashed...

Will an anti-virus program do this when I freshly installed it?

2. Now, .sys and .VxD are very different animals... renaming a .sys to .VxD or vice-versa, in the very best case, will result in things not working at all...

Really cause the ONE time it did work was because I used that renamed .vxd file , but maybe thats why it broke after installing avast...

Edited February 14, 2014 by Flasche

[jaclaz]

Ok, a nice step in the nice direction (but not enough).

Basically, it seems to me like - since you failed at following the normal procedure of installing the thingy - you decided that you could make it work manually.

This usually tends to end up in a mess.

And it is not like you can move (or rename) files "at random" and expect anytime soon to have it working, compare with:

http://en.wikipedia.org/wiki/Infinite_monkey_theorem

No, you CANNOT rename a .vxd to .sys (actually you CAN, but it won't work).

Probably your recalling the sequence of events is incorrect OR the .vxd is not used at all.

A good step forward would be if you could provide a link to the actual installer you tried, so that people can have a look at what is in it.

Is it this one?

http://support.linksys.com/en-us/support/adapters/WUSB54AG

File WUSB54AG-v1.0_dr.zip?

Avast is unlikely to be interfering with the thingy (though it's possible) in any case if it quarantined or deleted a file, it should be noted on it's log.

Depending on your current setup (which you haven't yet described, actual hardware, details on OS install, disk drive/partitions, etc.) it may be faster to test on a new install of the whole OS, or if you have another PC capable of running a VM, test what happens on a new install in the Virtual Machine.

A possible source of issue could be the kind of modifications (like - say - having used 98Lite or similar and/or tweaks) you made to the installed Windows Me.

Maybe you are further confusing the actual drivers with the tools in the Utility folder?

A good idea would be if you could read the contents of the .inf file WUSB54AG.inf AFTER having duly studied this:

http://www.wd-3.com/archive/InfFiles.htm

(besides the nice way it is written , it is also a very good introduction to .inf files and driver installation )

jaclaz

[Flasche]

INF Files for Bears of Little Brain

May 1, 2003

Brian Catlin

Just the other day, while walking through the hundred acre wood, I was accosted by the local fauna.

"Excuse me", asked a small pink pig. "B-B-B-But do you know anything about Windows Device Drivers? Because, if you do, our friend here needs some help", he said, pointing to a rather rolly polly teddy bear.

"What kind of help?", I asked the little bear.

"Well", replied the little bear, "I am a Bear of Little Brain. I just wrote a Windows Device Driver, but I dont know how to install it".

"What you need to do, is write an .INF file, which describes your driver and the device it controls, to the Windows operating system", I said. "Uh, by the way, what device does your driver control?".

"It is a hunny filter. It removes dirt, bees, and other impurities in hunny. It is my own invention.", he said rather proudly.

"Hmm", I thought to myself, "not bad for a Bear of Little Brain".

"Do you think, that is to say, do you know how to write one of these 'Dot Eye Eneff' files?", the bear asked.

"Sure, why dont we all sit down right here, and Ill tell you all about .INF files – Hey, wheres everyone going? Come back! Theyre not that bad!"

The small group of animals slowly reappeared, one by one, with more than a little trepidation in their eyes.

"Dont worry, .INF files arent nearly as bad as you think", I said, trying to sooth their fears.

"W-W-Well, thats n-n-not what m-m-most p-p-people say", said the little pink pig, clearly frightened.

"Calm yourself my little friend, nervous eaters dont grow up to be big tasty – er, healthy pigs", I said.

The little pig calmed down noticeably, but still regarded me with suspicion.

I'm done here. Auf Wiedersehen.

[dencorso]

INF Files for Bears of Little Brain

May 1, 2003

Brian Catlin

Just the other day, while walking through the hundred acre wood, I was accosted by the local fauna.

"Excuse me", asked a small pink pig. "B-B-B-But do you know anything about Windows Device Drivers? Because, if you do, our friend here needs some help", he said, pointing to a rather rolly polly teddy bear.

[...]

I'm done here. Auf Wiedersehen.

No, wait, stay! You know you're welcome here, and jaclaz meant no offense at all... and that text, despite being framed as a fable, is quite good. Do persevere!

[submix8c]

Never ever EVER read just part of something.

The remainder clearly explains the basics of INF files.

[jaclaz]

Sure , it is just a funny way to write an introduction, no offence whatever implied or intended (rest assured that IF and WHEN I might attempt to offend you, you will see the difference , and you will be really offended ) .

It is actually an excellent and detailed article on the matter, just read after the first few joking lines, I recommend that paper since years, proof:

http://reboot.pro/topic/1966-useful-info-on-inf/

jaclaz

Edited February 14, 2014 by jaclaz