EDIT: Mobo problem **FIXED!**

[Damaged]

Oh, no offense taken. I was just feeling my oats a little I guess. And I forgot that you don't need a newsreader to view newsgroups these days. It's still a better way, but it's not the only way with sites like http://www.deja.com and others around these days.

 

[fitzm]

This time bios.vxd was not requested but, pci.vxd was requested and it would not point to the win98cd for the file. Anyway, here is the new IRQ list and nothing even resembling "advanced power management support" or ACPI is is in system devices.

0: System timer
1: Standard 101/102-Key or Microsoft Natural Keyboard
2: Programmable interrupt controller
3: Communications Port (COM2)
4: Communications Port (COM1)
5: Creative SB Live! Value
5: IRQ Holder for PCI Steering
5: VIA Tech PCI to USB Universal Host Controller
6: Standard Floppy Disk Controller
7: ECP Printer Port (LPT1)
8: System CMOS/real time clock
9: Creative SB16 Emulation
10: Adaptec AHA-2940U/AHA-2940UW PCI SCSI Controller
10: IRQ Holder for PCI Steering
11: IRQ Holder for PCI Steering
11: Lucent Win Modem #2
12: PS/2 Compatible Mouse Port
13: Numeric data processor
14: Primary IDE controller (dual fifo)
14: VIA Bus Master PCI IDE Controller
15: Secondary IDE controller (dual fifo)
15: VIA Bus Master PCI IDE Controller

 

[Slikkster]

Ok...a few things:

The file "pci.vxd" is in the "base6.cab" file on the CD. If you need to find what .cab file a Windows File is in, here's what you do. Click Start, then Find, then Files or Folders. Now, in the box that comes up, enter the following:

"Named:" "*.cab"
"Containing Text:" "whatever your filename is goes here"
"Look In:" "wherever you have your CD files"
"Include Subfolders" "checkmark in this box"

Obviously, don't use the quotation marks for any of this, so it should say:

Named: *.cab
Containing Text: pci.vxd
Look In: cdrom drive or wherever you have the cd files
Include Subfolders checked


Always use the "*.cab" for the named box when looking for files on the Windows CD.

If you have Winzip, you should be able to doubleclick on a cab file to view it's contents. The reason I say this is because one cab file might have "pci.vxd" and some other cab file might have "xpci.vxd" or something because it contains the "pci.vxd" text. Comprendo? So, you want to know exactly which one.

So, do this for whatever other files Windows can't find when installing the plug and play fail safe bios.

You didn't mention whether you tried the USB under the scenario so far...did you?

One other thing to try once you have the plug and play fail safe bios installed is to rename that usbhub.sys file back to it's original state if it's not working correctly still and see if it makes a difference. We've been making changes all along and it's important to start with a clean slate and go from there. So, here's the order of importance:

Finish installing the Plug and Play Fail Safe Bios.
Try the USB.
If it doesn't work, let's go back to the original USB file, as everyone else seems to have no problem with it on this motherboard.
So, you'll rename usbhub.sys to viausb.sys, then rename usbhub.bak to usbhub.sys.
Reboot
Try USB again.
Report back.

Good luck.

 

[fitzm]

I have tried the scenario on the previous post, sorry I forgot to mention it. Plug and play bios (fail safe) is installed under system devices. But, camera is still not recognized with .bak file and viausb.sys file renamed. When those two files are returned to normal the camera is recognized but the program freezes still. The bios.vxd file is in the driver files details and also acpi.sys in the plug and play bios(fail safe)folder under "system devices". Is the fail safe bios installed?

 

[Slikkster]

Yes, it should be installed just fine. Now, we have to do more methodical stuff for a bit. Sorry, but that's the only way


Go into Device Manager, then go to the Sound, Video, and Game Controllers Section. Doubleclick on the "Creative SB Live Value" entry. Then, check the box that says "Disable in this Hardware Profile". Do the same for "Creative SB16 Emulation" in Device Manager. Then reboot. Try the USB stuff again (verify that Creative SB Live Value and Creative SB16 Emulation has a red X's over them to indicate that it's disabled after you reboot. Also, you should have no sounds now in Windows.)

If no difference, go back to Device manager and Enable the SB Live card and the Creative SB16 Emulation by removing the checkmarks in the Disable in this Hardware Profile boxes. Then, go ahead and disable your Adaptec Controller. Reboot. Try the USB.

Reenable the Adaptec if there's no change and
Disable the Lucent Winmodem. Reboot. Try the USB.
Reenable if no change.

Report back. Make sure you reboot before trying USB each time you disable a hardware item.

 

[fitzm]

No change. You did want me to leave the alternate file names in the windows/system32/driver folder right (.bak & .sys). The software freezes with default folder names regardless of which hardware is disabled or enabled in device manager. Just the message to "shut down any other application using the camera" pops up but the program at least does not freeze.
My burner has worked flawlessly on this board but I was curious if the message on startup that says: SCSI BIOS not installed! is talking about an onboard controller possibly built in to some boards and this message is just a general message by award or asus since obviously my uw card has its own bios right? Oh and my printer won't print some times but if I put all default settings back it does o.k. My modem will only connect at 21,000 or less (except for one time this morning) which on this free winmodem from buy.com has never been less than 45,000 bps unless I go back to default settings. Is this just normal considering all the changes and stuff we're doing right now?

 

[Slikkster]

I'm not sure what you mean about "default settings" for everything you're referring to.

The Winmodem shouldn't be affected unless it's disabled, of course.
The connect rate isn't a function of anything we've been doing.

Are you saying the printer doesn't work right under certain circumstances? Has it ever worked in USB mode at all? Or is this in parallel print mode? Yet you say it works consistently using "default settings". On that, I am unclear.

Yes, I did want you to try both the regular usbhub.sys file that comes with Windows AND if that didn't work, rename it to usbhub.bak and rename viausb.sys to usbhub.sys and try again with hardware disabled.

Once you've done all of that, I would recommend actually moving cards around in your pci slots. In other words, pull a couple of cards out in their slots, then switch them so that card A is in Card B's slot, and vice versa. Try the USB again after Windows redetects the cards.

This is all tedious work, I know. But since there doesn't seem to be any real documented problems such as this other than yours, it has to be done.

One more thing for now...please find the file "uhcd.sys" on your hard drive. RIGHT-CLICK on it, choose Properties, and then click on the version number. Tell me what version it is.

 

[Slikkster]

I hate to write out of sequence, but I found something else on the net that might help. It's an easy check to see if it will work, and if it doesn't, you just set it back to original settings.

(If you're just now reading this post and my previous post, try this first to save some effort):

Boot up and go into your bios. You want to tab one over to the Advanced section, then on the Advanced Menu that appears, get into the "Chipset Configuration" area. Look for 2 entries in the mix of other settings here:

"Read Around Write" (enabled by default)
"CPU-DRAM Back-Back Transaction" (enabled by default)

I want you to toggle both of those to "Disabled". Then exit the bios, choose "Save Settings" when prompted, and boot into Windows.
Try the USB under the following scenario:

You are using the Viausb.sys file that has been renamed to usbhub.sys

If no help, then go back to the original usbhub.sys file and reboot.
Try USB stuff.

If no good, go back into the bios and reset those two settings to "Enabled".

Then try the stuff in my previous post about moving cards around.

 

[fitzm]

Sorry, but I haven't been able to get online for a while. My modem is freaking out or something. I'm hoping it's just the line.

By default settings I meant putting things back to their original settings, file names, bios settings, etc. which I thought was helping but now I don't know what the heck is going on.

My printer never worked on USB but flawlessly on the parallel port. I'm wodering if I pressed something I shouldn't have because anything I changed or altered per your instructions went back to normal with no obvious side effects or problems at all (bsod or crashes etc.).

I don't care right now anyway. It's probably something simple and if worse comes to worse I can just re-install the software for the printer right?

I have a Diamond ISA modem only a couple months old for 30.00 lined up and hopefully that will connect faster than the 45,000 max connect rate I have been getting anyway.

I'll reset bios settings as you requested then do the old switcharoo with the cards.

Oh, the version of UHCD.SYS = 4.10.2223

 

[Slikkster]

Ok Fitzm, assuming there's been no change with the card swapping, let's make absolutely sure you have all the right USB files loading.

Go to this webpage:

http://support.intel.com/support/createshare/camerapack/usb/23729c.htm

Now, follow the directions to extract/install ALL of the files listed EXCEPT "UHCD.SYS". This will ensure there's no file version mismatches. The uhcd.sys file you already have is the most current, and is the file that Microsoft provides to patch VIA-chipset pc's like yours, so we'll leave that one alone.

So, you'll be extracting the following files:

KS.SYS
MSKSSRV.SYS
STREAM.SYS
SWENUM.SYS
USBCAMD.SYS
USBD.SYS
USBHUB.SYS
USBINTEL.SYS

As the web page says, they are located in the "base5.cab" and "driver20.cab" files on your Win98SE CD. And ALL of these files go into your C:\Windows\System32\Drivers folder. If you get any messages when extracting that you'll be overwriting files already there, just say OK, and continue with it.

Note: Before doing this, restore your "usbhub.sys" file to it's original state, meaning if you're using the viausb.sys file RENAMED to usbhub.sys, make sure you rename it back to viausb.sys for now.

So, the process as follows:

1. Restore your "usbhub.sys" file to the original Windows version by renaming the VIA-version of that file back to viausb.sys and then renaming usbhub.bak to usbhub.sys.

2. Follow the instructions on the webpage posted above from Intel to extract and install all of the files listed EXCEPT "uhcd.sys". Extract all the other files listed on that webpage to the c:\windows\system32\drivers folder.

(Do NOT rename the viausb.sys file after extracting/installing the usbhub.sys file from the CD...let's try it with the normal Win98SE driver right now)

After doing this, reboot and try the USB stuff.

I'm running out of ideas, man. And you're probably getting tired of all this, too. But this step -- making sure that all the USB files are the correct ones -- at least rules out a possible problem.

 

[fitzm]

Just finished swapping this morning. No luck. It does get a little frustrating but I'm good as long as you are. Downloading files now.

 

[fitzm]

Extacted files. KS.SYS was the only file not on the cd (driver20 folder) but, it is in the driver folder on the hard drive. Also, there is a .001 file : KS.001 next to it in the driver file. GM.DLS is the only other non-system file in there. All the rest are system files. Another thing, which I wish I would have checked to see if it was there first, is that I received the prompt to "overwrite" all files except: MSKSSRV.SYS & USBINTEL.SYS. Does this mean the files were not there in the first place?

Off topic: Is there something (program or whatever) that I can use to see if the modem is screwy or receiving all the signal strength it can from my line?

 

[Slikkster]

Looks like the Intel site was wrong on "ks.sys"...according to Microsoft, it's in the "base5.cab" file. Please look there and please extract it.

The answer to your other question about the files that were not overwritten is yes, they weren't there to begin with, apparently.

As for the modem, I'd be just checking the connection at the wall and at the pc (pull the phoneline from the modem and reconnect it and the same at the wall jack) and also try temporarily removing other phones/phonewires installed in your house off the jacks to see if they might be interfering with your modem connection (sometimes a noisy phone or answering machine throws static on the line).

Please advise on what's happening with the USB after extracting ks.sys

If you can't find the file on "base5.cab" where it's supposed to be, then use the Find Files/Folders, and put:

Named: *.cab
Containing Text: ks.sys
Look In: Cdrom drive
Subfolders: Checked

 

[fitzm]

SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Slikkster, you are da man. I can't thank you enough. ( my second child: Slikkster Fitzmaurice, hmmm has a nice ring to it.)

Why don't some files extract from the win98 cd? I wonder how many other programs that don't run correctly are from a lack of a needed file.

Anyway, I mailed Anand and asked him to create and give you an "Editor's Choice" Good Samaritan award. You deserve it.

Thanks again Slikkster.

Anybody reading this post, please mail Anand and let's make Slikkster the first recipient.

 

[Slikkster]

Argh! I went back over all my posts (and yours) from the beginning and I found another potential problem. Remember when you told me in the original thread that there were lots of files you couldn't find on the CD that Win98 needed? (like "ksdata.ax", "ksinterf.ax", etc.)?

Well, I pointed you to a download site on the IBM webcam page where you can download and auto-install all the required files to their respective folders on your system. Here's the potential problem. I just checked the version numbers of those files, and they are all for the ORIGINAL version of Win98, NOT Win98SE. And this was before I realized that the Win98SE CD DID have these files on it...it's just that your installer couldn't find them on the CD. So, there's a bunch of files for USB that have to be updated so they are the Win98SE versions. I've prepared a list for ya. The list contains the filenames, and the *.cab folders they reside on on the CD.

So, here we go. Please make absolutely sure that ALL these files are updated/extracted/installed.


The following files are to be extracted/installed to the c:\windows\system folder:

ksclockf.ax Driver11.cab
ksdata.ax Driver11.cab
ksinterf.ax Driver11.cab
ksproxy.ax Driver11.cab
kstvtune.ax Driver11.cab
ksuser.dll Driver12.cab
ksvpintf.ax Driver11.cab
kswdmcap.ax Driver11.cab
ksxbar.ax Driver11.cab
vfwwdm.drv Driver16.cab
vfwwdm32.dll Driver13.cab

---again, the above list of files should go into the c:\windows\system folder.

The following files are to be extracted to the c:\windows\system32\drivers folder:

Stream.sys Driver20.cab
ks.sys Base5.cab

--again, these two files, "stream.sys" and "ks.sys" go into the c:\windows\system32\drivers folder.

Now, you probably already extracted ks.sys from my last post. Just make sure you have.


Now you should have all the correct files for the USB for Win98SE!

Try the USB Cam and printer again.

If you still have problems, there's one more thing to try, but do this for now.

Also, after you've done that, please go to Device Manager, click on your Lucent Winmodem entry and go to the Drivers Tab, then Driver Details. Tell me what version of the drivers you have there for the files. All Lucent Winmodems use the reference drivers from Lucent (no matter what brand you have). The more recent drivers make a big difference. I can point you to them after you tell me what you have installed now.

I've used 3 different Lucent chipset winmodems. I think they're very good modems, as good as anything else I've ever used if not better.

 

[fitzm]

I'll check out and update to current versions where needed.

 

[Slikkster]

Wow man, I'm so happy about that! I feel a little stupid for not realizing the problem earlier but sometimes it takes awhile for all the pieces to sink in. That's why going back and rereading all our progress over time helped out...somethings became clearer after the fact.

You were a real trouper in following along all this time, too, so my hat's off to ya.

If you still want that Lucent driver website, here it is:

http://www.808hi.com/56k/x2-lucent.htm

Lots of good info about the Lucent Winmodems here. You want the "Firmware Upgrade" link on this page. It's version 5.75 at present, but this page tells you everything you need to know about Lucent modems, how to upgrade the drivers, etc. On the firmware upgrades link, you want the driver (5.75) at the top of the page, NOT the brand name stuff at the bottom. The 5.75 driver is the latest.
Of course, if your modem is working fine now, upgrading the driver is up to you.

Edit: If you want to make sure your Windows Add/Remove programs finds your Windows CD correctly, you'll have to edit the registry to see what it has set for the "Install Path". Here's how to get to it.

Click Start, then click Run, then type in "regedit" (no quotes) and hit OK. Now, click on:

1. HKEY_LOCAL_MACHINE
2. Software
3. Microsoft
4. Windows
5. CurrentVersion
6. Setup

So the path is:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup


Now, in the Setup section, you'll see lots of settings. Scroll down the list until you see "SourcePath". To the right of that entry is it's value, which should be your cdrom and the Win98 folder on it, in other words, if your cdrom is drive D:, it should say "D:\Win98\".


Make sure there's a backslash after the folder name. So, again, assuming your CDROM is your D: drive, your listing in the Setup section of that registry key will say:

SourcePath D:\Win98\

Doubleclick on the name "SourcePath" to edit the path itself. Of course, modify my example to point to your CDROM drive letter if it's different than D:.

Exit the registry.
Reboot.


(Fix the Sourcepath issue in the registry before doing anything below here)

New subject: With all the changes we made, you now effectively have NO power management going on on your PC...No ACPI, NO APM, etc. So, you won't get the benefits of things like shutting off your monitor/hard drives after a period of idle time. Your motherboard has even more powerful options with ACPI enabled. So, it's up to you whether you want to re-enable your power management or not.
I'd understand if you want to leave well enough alone, but since the USB problem was a files issue and not a hardware issue, it shouldn't (famous last words) present a problem.

So, IF you want to re-enable ACPI, let's undo that registry setting we did awhile back.

Click Start/Run/type in "regedit" (no quotes) and click OK.
Then click on the following

1. Click on HKEY_LOCAL_MACHINE
2. Click on Software
3. Click on Microsoft
4. Click on Windows
5. Click on CurrentVersion
6. Click on Detect


So the key you want is:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Detect

Now, in a previous post, I had you create a "DWORD" string labeled "ACPIOption". It's current value should be 0x00000000 (0)

DoubleClick on the key "ACPIOption". You'll be able to change the value here. It defaults to "Hexidecimal". I want you to click on the "Decimal" circle so it puts a black dot in that circle, then change the value from "0" to "1". Then, click on OK.

After doing this, it should say:

ACPIOption 0x00000001 (1)


Now close the registry and reboot. After rebooting, go to Control Panel. Then, click Add/Remove Hardware. Let it search for BOTH Pci AND Non-PCI hardware. After that, it will tell you what hardware it found. Click on "Details". It should show you that it found the ACPI Bios. Click "Finished". It should install ACPI.

After it redetects (although it may not have to because it did it before and might have saved the registry settings it found), let Windows finish booting and then go to Device Manager and see if everything is running without conflicts.

If everything is running OK in Device Manager, you should be good to go!


Congrats again and thanks for the kind words. Happy USBing...

 

[LBM1A]

CONGRADULATIONS GUYS!!!!!!!! Im glad to see this finally come to a happy ending.. Slikkster I said it once and a i'll say it again You are one Hell Of A Guy!! It has been like watching a movie or reading a good novel. Good Luck to you guys..

P.S. Got my Vote!!

 

[fitzm]

OOPS! I actually just deleted that ACPIOption by right clicking on it earlier after the USB was working and before I read this post and re-booted and it went back to ACPI in the device mgr - system devices and things seem o.k. at least no flags anywhere so far. Is there something else I should look in to see if everything is o.k.?

 

[Slikkster]

No problem. If your IRQ list now shows:

"9: SCI IRQ used by ACPI bus"

and any IRQ's that use "PCI Steering" are preceded by "ACPI IRQ Holder for PCI IRQ Steering" then you should be all set. That registry entry was to Disable ACPI, so deleting it allowed for auto-redetection, apparently.

You should also see an icon in Control Panel for "Power Management" that allows you to set times for when to shutdown your monitor and hard disks after a period of idle time.

Just confirm that the ACPI stuff above shows up in your IRQ list. And glad to hear that all is OK!

 

[Slikkster]

P.S. Thanks LBM1A for the kind words.

 

[fitzm]

No problems. Everything is exactly as you said.

I forgot to thank you for the Lucent fix also. My modem actually is at 48,000 right now. WOW! I never got above 45,500 before, with this modem, ever.

I'm still waiting for Anand's reply on the Editor's Choice G.S. award category approval and implementation. I'm not blowing smoke here. I really think people like yourself deserve recognition for their selfless deeds.

 

[Slikkster]

Outstanding. I believe we can now officially close this thread. Nice work!