Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

HELP! Desktop is odd...not in safe mode..mouse driver?

Sep 7, 2005 10:59PM PDT

I am on the kids computer at the moment...
On my computer today everything was fine, after 'burning' 2 cds with my Ashampoo program I decided to play a regular cd music and my windows media player-recent version 9 -I think, told me Windows had a problem and could not find the file?My cd-rom is drive E.Had no prior problems...worked wonderfully.I noticed in the little window on the music player on the screen that tells you what you choose to play said audio CD.But on fiddling slightly a couple of times I brought up audio cd E but it would not stay there.
I have Windows 98SE and recently was overhauled by a repairman and worked wonderfully after everything was updated including drivers.I have 256MB RAM.
Everything is always up to date...AdAware Se personal,Zone Alarm free,Spybot S&D...Spywareguard and spywareblaster also AVG free.
I decided to turn off the computer and restart...BUT...after AVG saying no viruses in rebooting, when the desktop came on it was an odd colour and graphics was different.It also was not in safe mode...BUT the mouse pointer was not there.I eventually figured how to use the keyboard to try and figure out what the problem is.
I rebooted several times and the screen remains the same!
Eventually I found the mouse was a problem.
In checking out the device manager (after scandisk fixing a couple of problems that did not help)I find the mouse driver is not found.
Under PS?2 compatible mouse port I looked at the driver files to find 3 items: C:\WINDOWS\SYSTEM\VMM32.VXD (vmouse.vxd)
'' '' '' \msmouse.vxd
'' '' '' \mouse.drv
The second and third items were fine...But the first item told me it was not working.
I tried to update driver and windows said it was the best one to use.
I also pressed Ctrl/Alt/Delete a couple of times..( had trouble shutting down) and once there was nothing in the popup except vsmon.
I decided to swap computers until I get some help!!!
Thanks for now
Mandy

Discussion is locked

- Collapse -
Mandy, See If This Helps...
Sep 8, 2005 2:41AM PDT

...although it appears like you've got more than one issue here...

First, the "Vsmon" listing is probably for the ZoneAlarm firewall. On a Windows 98 machine, you should be able to do without it for a while...so try turning it off and see if it makes a difference...Stop it from booting by opening ZA console, then, depending on your version of ZA, click on the "Overview" tab on the left side, click on the "Preferences" tab, then UNCHECK the box next to "Load At Start Up".

Next, try uninstalling the mouse, then restart the computer and Windows should recognize it again and reinstall the drivers for the PS2 mouse. Do it like this: Open the "Device Manager", then click on the + sign next to the "Mice and other pointing devices" listing. Highlight the specific PS2 mouse device that should now be displayed, then choose the "Properties" button, then click on the "Driver" tab. Now uninstall the driver, then restart the computer. BE SURE THE MOUSE IS PLUGGED IN CORRECTLY. Upon restart, the drivers should be installed correctly.

It also sounds like the video driver may have become corrupted...If you've got the updated video driver for your computer, then try reinstalling it.

And just as a precaution, please restart into Safe Mode, then run a full system scan with ALL of your antivirus and antispyware tools. These types of tools do a much better job in Safe Mode.

Hope this helps and let us know how it goes.

Grif

- Collapse -
(NT) Hi Grif,
Sep 8, 2005 4:56PM PDT

I am still on my computer ...using keyboard keys.
Unfortunately I do not have a Windows Installation disk.
I could possibly borrow windows 98Se from my brother-in-law.
I have a disk my repairman gave me...not sure what it is exactly for.
On it is written 'Gigabyte Motherboard GA-WMMC7'.
Colour is still strange and cannot play cd on Windows Media Player.'Windows Media Player cannot find the specified file etc.' is the message still.
Is it possible to download a driver for the mouse?
I do not get uninstall for the mouse but I get remove.
Have not done that.
Back soon
Mandy

- Collapse -
Mandy, Yep, 'Remove' Is Correct
Sep 9, 2005 2:37AM PDT

Please "Remove" the mouse from Device Manager, then restart the computer with the PS2 mouse plugged in. The "Gigabyte Motherboard" is probably the motherboard drivers, but it's hard to tell without actually looking at.

Just a thought here...have you tried running the Windows 98 equivalent of System Restore which is "scanreg /restore"? If not, then please do the following:

1. Restart the system in MS-DOS mode.
If the system does not automatically start in MS-DOS mode when attempting to boot into Windows 98, hold down Ctrl key during system startup until the Startup Menu displays, and choose "Safe Mode Command Prompt Only" from the Startup Menu.

2. At the C: prompt, type scanreg /restore and press Enter. You do not have to be in the C:\Windows\Command folder to run the command.

3. Choose which backup to restore. You should have a choice of registry backups from the last five days the system successfully booted. You can also restore other backups from either the hard drive or floppy disk. The backups from the last five days will be in the format RB00x.*, where RB stands for Registry Backup, and x is the sequence number of the backup. RB000.cab is the most recent backup.
__________________

You've got a number of things which caused issues at the same time and your suggestion to reinstall Windows 98SE is a good one. If the above steps don't help with the problem, you'll probably want to try the repair install of Windows 98. It installs "over the top" of itself and "should" allow you to reinstall Windows without damaging your personal documents. There are no guarantees here, so hopefully you have backups of those documents. In the end, you may need to completely reformat the hard drive and reinstall everything.

Hope this helps.

Grif

- Collapse -
Me again Grif....no good....
Sep 10, 2005 12:36AM PDT

I have gone into safe mode and done what you suggested with the mouse.When I rebooted Windows said it found a new device,installed it and booted.Getting into desktop and my mouse is still missing!Yet it worked fine in the safe mode.
As far as scanreg/restore...well the computer tells me there is no file.In safe mode I had to go to 'run' to do this...no C:.
So I looked for it in find files and folders...no luck.I also searched this way for the missing driver-by the way it is called 'VMM32.VXD(vmouse.vxd).
I located this in drivers.com and downloaded it....but it is sitting on my desktop as I cannot put it in a folder.I thought the correct path is C:WINDOWS/System/.
In my explore there is nothing but an empty folder for VMM32 and also drivers...But if you look in WINDOWS/System/win98 there is nothing but endless drivers and others.
I have the windows 98Se installation disk from my brother-in-law.Although it is not my system,I haven't even put it in the CD drive as I do not think it will work as I cannot get anything read in there(my E drive)
The computer will not acknowledge it...I have no idea why.And yes the colour is still odd.And the big ads often flicker.Recently the repairman fixed this computer and updated all drivers-I think it is covered by warranty for 3 months....but cannot afford extra cost at the moment if it is not covered.
I have been so frustrated with this thing...all day trying to get around the keyboard and locate the driver...to no avail...now I am working with a small window on my desktop....Sad
Sorry to grumble ...
Any more ideas?
Mandy

- Collapse -
Mandy, I Just Found This...
Sep 11, 2005 3:46AM PDT
- Collapse -
YES!!!!!!I have a mouse again.......still trouble with...
Sep 11, 2005 12:25PM PDT

Thanks heaps Grif you are a genius!!!!!
I found this yesterday but using the keyboard I did not save - I did not work out how-and because I did not save-of course the "garbage" was still there.
But since then have figured out the keyboard more and read the instructions fully!
Now unfortunately still have some problems...
A:Just tried to install google toolbar....for some strange reason it had dissappeared a couple of days ago during mouse trouble, and tells me in the address it is done.But it is not there.
B:Windows Media Player is drive E and even though it dissappeared during mouse trouble it is in my computer again.BUT putting the cd in to play the player comes up and then tell me Windows cannot find the specified path.In the little window that shows the path in the top right of the player it shows audio cd, when I drop down the box I see audio cd (E:)and it will not let me put that in the little window.It does start in autoplay until this message comes up.
C:Also during this time my display settings will not
change from 640 x 480 pixels / 16 colours to 256 colour /800x600 pixels...even though I click apply.Although I have just altered it again to try and will reboot as soon as I post this message.
Unsure if anything else ? is wrong (I'm hoping not).
My fingers are crossed!
Thanks tons so far
Mandy

- Collapse -
Mandy, One Thing At A Time...
Sep 11, 2005 2:21PM PDT

First, I suggest that you refrain from installing any extra stuff until you get the major issues fixed. Forget about the Google toolbar for now.

Second, Although Windows Media Player may not "autoplay" correctly, can you make WMP play the music by opening "My Computer", then double click on the "E" drive? Or possibly "explore" the "E" drive, then double click on one of the files inside? If it works, then we just need to fix the autoplay issue..Let us know if it works at all.

Third, It appears like the video driver needs to be reinstalled to fix your "colors" issue. To determine the video driver needed, RIGHT click on "My Computer", choose "Properties", then click on the "Device Manager" tab. When that opens, click on the + sign next to "Display Adapters" and a specific device will listed. Click on the device, then click on the "Properties" button toward the bottom of the window. When that loads, click on the "Driver" tab, then write down the "Driver manufacturer/provider", the "Driver date" and the "Driver version". Now visit the website of the driver manufacturer/provider and download, then install the appropriate driver for your video card.

Hope this helps.

Grif

- Collapse -
Grif, first and second...is it.....
Sep 11, 2005 7:42PM PDT

Windows Media Player actually does start autorun...I can hear it...the track numbers are in the players window,then windows media player cannot find the correct path.When I open my computer it shows when a disk is in there because the icon has a music disk icon.If I click the icon the player again comes up and track numbers are listed....again cannot be found...check correct path.I think something is wrong with e drive (cdrom) maybe it isn't being acknowledged it is there...or something?!

Next I have found intel site for driver and got the details...but my Belarc adviser,system information, device manager and system file checker all show no problems....should I still download the new install.I also read that the driver must be exactly the same and this driver (Intel (R) 82810-DC100 graphic controller, date 4-222-1999, file version 4.13.01.3004)has no support from intel anymore and is archived from what I understand after navigating this site.Is it still safe to download this.Scary in case I mess up...
Thanks
Mandy

- Collapse -
Grif...p.s. just found some more info....
Sep 11, 2005 8:32PM PDT

I realise I do not have any sound at all and haven't done at least a couple of ...did not pay any attention to this.
But just looked into controlpanel/sounds and find under sound name: none-and it is greyed out.
Looked at Intel Graphics Technology and a message on the screen tells me:The driver for this control panel Applet is not currently running or it is not available.
Also looked in Multimedia:Devices properties::Vortex AU8810 Wave Audio - Status driver is inactive but enabled due to an unknown problem.(I have 2 of the exactly the same listed).....Vortex AU8810 Wavetable MIDI - same message as above (again 2 of these).....
Vortex AU8810 Audio Mixer - same message and again 2 of them....and Vortex AU8810 Auxilary Audio only one of but same message.
In multimedia I also looked at AUDIO and found: Playback Preferred-No Playback devices and it is greyed out.....Recording - No Recording Devices and greyed out also.
Does this mean it is for sure the driver?
Thanks
Mandy

- Collapse -
Mandy, You'll Need to Install The Most Recent Audio Driver..
Sep 12, 2005 12:53AM PDT

...as well. That's why you have not sound and everything isn't working. It may also fix the Windows Media Player issue.

YES, you'll need to install the newest Intel driver for the video card. Despite Belarc, the video card definitely isn't working right. The driver DOES NOT have to be exactly the same but you DO need to verify the one you're downloading is supported on Windows 98. At the Intel site, this appears to be the most recent driver for you Windows 98 82810 chipset video card. You should be able to use the "English" download.:

Intel 82810 Graphics Controller-Graphics Driver [WIN9XE67.EXE, WIN9XM67.EXE]

Hope this helps.

Grif

- Collapse -
Grif...graphics is fixed!!!...I assume audio is next...
Sep 12, 2005 12:13PM PDT

Upon rebooting even though the graphics driver I checked seemed to be fine I had difficulty in my home page freezing several times...I had to reboot several times until I finally was able to get on the net.
I recieved a popup first of all before the desktop came up -at my password bit-telling me this is an illegal thing (Igfxtray was written in the top of it)...it also happened on my desktop and also a couple of times when the homepage froze during loading.I eventually got on the net by clicking an application for it to go to it's homepage.
No sound still and I looked in device manager and checked drivers....Everything appears fine although in -Vortex AU8810 PCI Audio in the driver details there are 22 files(?) and 2: AU10DOS.COM + AU10GM.ARL appear to be the only ones that say 'unknown' when I click each one.Otherwise I am not sure...
Thanks so far Grif,
You are a patient man,
And I'm trying to be (not a man Grin)
I just wish I understood why all these various things have happened as I touched nothing out of the ordinary and recently the repairman updated all drivers-or so he charged me for it, but in a place like I live with a population 13.000 ,word can get around quick if you're not reliable, and he supposedly is.
That's Life I guess...
Mandy

- Collapse -
Mandy, Yep, Sound Drivers Next...
Sep 12, 2005 12:34PM PDT

Download and install the newest audio drivers for your operating system. I'm not sure that Aureal is still in operation to support the old Vortex sound cards. Still, you should be able to find an appropriate driver by searching for: "Vortex AU8810 PCI Audio"

Why did this happen? Who knows, except that you have an older machine that may be getting to the end of it's usable life..And the simplest answer is: "Because it's a computer and who knows what they will decide to do at any given moment." Be sure to keep good backups of your important documents.

Hope this helps.

Grif

- Collapse -
Uh-Oh....not sure what's happened....
Sep 12, 2005 3:29PM PDT

I am sure I downloaded exactly the right driver, it put itself into C:Temp and unzipped itself.I then rebooted and went into safe mode...computer said I did not shut down properly so I checked device manager anyway and rebooted...but still no sound and desktop brought up an error ( in the toolbar was Hkcmd).
I went through windows update to get on the net again.
How do I check what I have done ...and undo presumably?
Sorry Grif....I thought I would be fixed,
Mandy

- Collapse -
Mandy, Try This...
Sep 13, 2005 2:39AM PDT

..in order to install the audio driver. There should be no need to go to Safe Mode. I'm assuming the unzipped audio driver files are still in the "Temp" folder. So...RIGHT click on "My Computer", choose "Properties", then click on the + sign next to "Sound, Video, and Game Controllers". Find you specific audio card, then highlight it and click on the 'Properties" button. When that loads, click on the "Driver" tab, and then click on the "Update" button. When that loads, you'll need to follow the prompts to "Search for a driver file better than now" and the "Specify a Location" and "Browse" to the Temp folder and maybe the driver subfolder where you should find a file with a .inf file extension. That will be the file which should install the new drivers. After installing the new driver, you'll want to restart the computer.

Hope this helps.

Grif

- Collapse -
Me again Grif....found this....?...still no good!
Sep 14, 2005 5:41PM PDT

I tried what you said and it has not worked....but looked closely at everythin in Start/Explore and all the details of what happens when trying to 'update driver'.Maybe this will help for a solution.
Found in Start/Explore several 'copies' of the driver in various paths, Vortex AU8810 PCI Audio; Aureal Semiconductor.These paths are:
C:GA-6WMMC7/Audio/WIN9x/AUREAL_WIN9x_405
/Chipset/INTEL INF/INF UPDATE
/Video/WIN9x/driver_vga_intel_81x_9xme/Graphics/support
win9x
C:Temp...(Aureal files are in here)
C:Unzipped/Temp (and here)
C:Unzipped/wavs/Vmm32...(according to properties 5 files in here, cannot see any icons)
C:Win 98...(Aureal files here plus a large number of drivers, win98 and various)
C:Windows/System/Drivers...(0mb info in here - empty folder)
C:Windows/System/Vmm32...(properties say 5 files here also cannot see icons)
C:Windows/System32/drivers...(inside drivers are 2 items,Gm.dls + Gmreadme)

I also on my desktop have a folder that I label 'downloads' and in here is 'Aureal-8810-v312'
I am sure this is the one I want and cannot get the path when trying to update driver with the wizard.

Now, going into device manager - highlight (Aureal)Vortex AU8810 PCI Audio- properties Aureal Semiconductor:3-25-2002
No driver files are required or loaded for this device..etc.And if you look at the bottom neither of the 2 boxes are ticked (disable or exists)

Looking at driver details when I update the option I have for select other driver is :
Vortex AU8810 PCI AUDIO
4-22-1999
Aureal Semi....
C:\WINDOWS\INF\AU10MMEN.INF (trying to find this path in explore and it is not there).

I did not know what path to put in but tried them all and wizard tells me the driver is the right one that I have so I select the path and wizard tells me location of driver is:C:Windows\Inf\Other\Aureal~2.INF.

Again there is no path in explore windows\Inf.

I looked up start/find files and folders and typed in AU10MMEN.INF and find the only result is the path:
C:\GA-6WMMC7...On the find files and folders result I scrolled across and read 51KB and setup information.

Doing the same and only typing AU10MMEN I find 3 folders:
au10mmEN C:GA-6WMMC7/Audio/WIN9x/AUREAL_WIN9x_405
size 1KB security catalogue

au10mmEN C:GA-6WMMC7/Audio/WIN9x/AUREAL_WIN9x_405
size 51KB setup information

au10mmEN C:GA-6WMMC7/Audio/WIN9x/AUREAL_WIN9x_405
size 51KB BAK file

I think that is all for now.....I have given you everything I think I can and written it exactly as I read it ....I am hoping this will help.
Thanks again Grif
Mandy

- Collapse -
Learning ''order''
Sep 14, 2005 11:38PM PDT

"Order"

May I suggest a means of some order for when you download something from the Web:

a. First, create a folder somewhere on your harddrive/a partition labeled downloads.

Second, when you perform a download, have Explorer open, access the downloads folder by clicking it so that it is highlighted, click File, New Folder, and since the folder is already highlighted for naming, name that folder something which coincides with the item being downloaded. For instance, I have a folder under my "Downloads" folder labeled "Drivers" and subfolders off it labeled such things as Video, CDDrive, Fitness, USB and etc. Every single download is performed only in the downloads folder which after a while you will also learn that when installing, the files necessary for access when something pops on the screen, is located somewhere there. IMO, never use the Desktop for a download location regardless of instructions read.

b. (according to properties 5 files in here, cannot see any icons)

Start Windows Explorer, click the View, Options. Click the View tab, click Show hidden files and folders, and then click OK.

c. Now, going into device manager - highlight (Aureal)Vortex AU8810 PCI Audio- properties Aureal Semiconductor:3-25-2002
No driver files are required or loaded for this device..etc.And if you look at the bottom neither of the 2 boxes are ticked (disable or exists)


The why this is happening to you is explained in "How Windows Determines the Most Suitable Device Driver to Install During Setup (Q279112)." You need to arrange your downloads and supercede those already in affect.

For instance, when I access a driver for a video adapter card, you have several option of dealing with it. First is the Driver tab where you'll fond both two buttons labeled Driver File Details. . . and a button Update Driver. . .. After clicking the latter button you should simply click the Next > button for another context menu which has something to the effect:

Search for a better driver than the one your device is using now (Recommended)

Display a list of all drivers in a specific location, so you can select the driver you want.


What I'm try to covey is that option #2 list those items which you'll generally see if you had progress through the Control Panel, Add New Hardware to add a new peripheral. The only difference from that stand point and where you are with this device driver is that a similar device has once been installed, and the context menu takes you directly to the type of device you're concerned with. If you going to change the driver that has once been installed you'll need to progress this way. After selecting the button mentioned in the latter above, you then click the Next > button that then list all kinds of drivers located on the system -- already. When the Update Device Driver Wizard (named in the top colored bar) is displayed and the drivers listed and where you can usually select what you want -- but you know it isn't there since you've just download it, use the button labeled Have Disk. After that, you have to provide the location of where the driver is found so that Windows can install it. As I've already mentioned, if all downloads are in one place, that place is easily found.

- Collapse -
O.K. cursorcowboy....1 quick question..
Sep 15, 2005 10:46AM PDT

To help me understand here.....If there are files in several places how do I know which is the one that I need to 'point' the update wizard to? I am thinking there are files in too many places...isn't that gonna confuse the o.s..
Don't I need to delete some of these...and I don't understand why there are what appears to be the same files for the Aureal driver in more than one place.
Vmm32 is to do with the graphics too and this is also in more than one place- or at least the folder is.I thought the graphics were fixed - but I must have done something not quite right as I get this 'igfxtray error' on the screen as desktop is loading and realise this is to do with the Intel driver I have downloaded and installed.
And what do I do with the desktop Aureal?...as I think that is the one that I downloaded and is the one that ought to be accessed and loaded into the system.
Now I am getting more confused....I think I need to really look at your info to take it in.....I am certainly realising how much of a newbie I am!
I will go back to reread your message for now...
Thank you
Mandy

- Collapse -
RE:
Sep 15, 2005 10:48PM PDT

A. If there are files in several places how do I know which is the one that I need to 'point' the update wizard to? I am thinking there are files in too many places...isn't that gonna confuse the o.s.

Could I suppose. However, the one reference I gave in my original explains how Windows goes about selecting a driver for a particular device. But, even though P&P may select a driver, it does not mean it is the appropriate one in every case. If it were my system, I'd start by uninstalling and removing drivers from the area I'm working on and then ensure I have the driver I want in a specific place and start from there. If it didn't work as expected, I get another driver, and start all over again.

B. Don't I need to delete some of these...and I don't understand why there are what appears to be the same files for the Aureal driver in more than one place.

Can't answer the second part since I'd have to go through each segment of a downloaded driver package to ascertain if they contained exact names but contents were different.

C. Vmm32 is to do with the graphics too and this is also in more than one place- or at least the folder is.

Depends on whether we mean ''The file'' or folder. If a folder, it would depend on what is in that/those folders. For instance:

The real-mode boot loader Win.com loads the monolithic file VMM32.VXD into memory during boot and then loads other dynamic virtual device driver (VxDs) files contained in the Windows\System\Vmm32 folder. Please note that any of the files in that folder, to include the Vmm32.vxd file itself, may have become corrupted and cause system anomalies.

a. Drivers contained in this files is a long list located in the system registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD

b. Additional files loaded besides those in this list are any VXD files present in the ''C:\WINDOWS\SYSTEM\VMM32'' folder.

c. The VMM32 program switches the computer's processor from real-mode to protected-mode and is a three-phase VxD initialization process in which the drivers are loaded according to their InitDevice name instead of the order in which they are loaded into memory. VxD loads are carried out in the following sequence, outlined and described in ''Q127970'':

(1) SYS_CRITICAL_INIT (SYSCRITINIT):

Interrupts are disabled during this phase. This gives VxDs time to prepare for device initialization without being interrupted by the system. No file I/O is allowed during SYSCRITINIT, so all SYSCRITINITs are not written to a Bootlog.txt file until after SYSCRITINIT is complete for all VxDs.

(2) SYS_DEVICE_INIT (DEVICEINIT):

The bulk of the VxD initialization takes place during this phase. File I/O is allowed during DEVICEINIT so each VxD's DEVICEINIT is logged as it occurs. The one exception is during Ifsmgr's DEVICEINIT. Ifsmgr takes over the real-mode file system and disk I/O is not allowed until Ifsmgr's DEVICEINIT succeeds. For this reason, Ifsmgr does not appear in the DEVICEINIT phase.

When a DevLoader VxD is called, it loads other drivers it is responsible for regardless of their InitDevice order. The DevLoader examines the Registry and finds drivers (for example, port drivers or .mpd files) and any associated support drivers and then initializes the device associated with them. During this phase if a VxD failed to initialize, or it was unable to properly communicate with a hardware device or service it, an error is renders and is typically due to incorrect hardware settings or a service was not present.

Remaining static VxDs continue the initialization phase and certain dynamic VxDs may also begin during this phase even though they do not have a SYSCRITINIT phase. In addition, dynamic VxDs may load anytime after Windows starts.

(3) SYS_INIT_COMPLETE (INITCOMPLETE):

VxDs that successfully pass the InitComplete phase should work properly. A VxD reflected in one of the previous phases which was not successfully initialized, is unloaded from memory.

(4) GUI Components:

After all static VxDs are loaded, the Krnl32.dll, Gdi.exe, User.exe, and Explorer.exe (the default Windows shell) files are loaded.

d. The WIN32.VXD file is a monolithic file (a file which can be extracted using System File Checker tool and then by reinstalling Windows so that the file is correctly rebuilt). However, this does not mean that some errant x.VXD somewhere else isn't the major culprit and is the cause of a system problem which did not get corrected through this process. I know that many users have never been able to figure this out -- including me for sometime, and was left with the option of wiping the entire system and starting from scratch. An in-depth discussion concerning the monolithic file Win32.VXD file, please read through the TechNet article ''Setup Technical Discussion - Chapter Five''.

e. Supplemental reading:

(1) ''Invalid VxD Dynamic Link Call from... (Q137335).''

(2) ''Windows 95/98 Boots Directly to ''Shut Down'' Screen (Q14189Cool.''

(3) ''Initializing Device IOS Windows Protection Error (Q263466).''

(4) ''Error Message: While Initializing Device IOS an I/O Subsystem Driver Failed to Load... (Q31110Cool.''

D. I thought the graphics were fixed - but I must have done something not quite right as I get this 'igfxtray error' on the screen as desktop is loading and realise this is to do with the Intel driver I have downloaded and installed.

Using a ''Google Group'' search on your reported error there are many items covered but generally indicates the error comes about by subsequently installing a driver version older than the last. I believe you'll also find instructions at the Intel site for resolution or if not an Intel driver, the site you've been dealing with. Maybe they offer ''Tech'' support too

E. And what do I do with the desktop Aureal?...as I think that is the one that I downloaded and is the one that ought to be accessed and loaded into the system.

I assume you mean a download copy to a folder on the desktop. If so, there isn't any reason the content of that folder be placed in a folder created for such as I explained earlier for downloads -- then delete the desktop folder which would then be empty. Then use the basic steps I outlined earlier Display a list of all drivers in a specific location. . .

F. I am certainly realising how much of a newbie I am!

Everybody was there at one time and bought the ''T-Shirt'' too.

Good luck.

- Collapse -
Thanks Cursor....you know how to boggle the mind always....
Sep 15, 2005 11:13PM PDT

you spend a bit of time answering in such detail...thank you heaps.
Trouble is it takes me a million times longer to try to get all the technical terms to stay in my head...BUT I am working on it...including your other marathon post....do you work in a library? LOL Grin
Mandy

- Collapse -
(NT) (NT) No. But, I've been told I'm the library.
Sep 16, 2005 10:25PM PDT
- Collapse -
RE:
Sep 10, 2005 11:27PM PDT
I have gone into safe mode and done what you suggested with the mouse.When I rebooted Windows said it found a new device,installed it and booted.Getting into desktop and my mouse is still missing!Yet it worked fine in the safe mode.

So I looked for it in find files and folders...no luck.I also searched this way for the missing driver-by the way it is called 'VMM32.VXD(vmouse.vxd).


You're overly concerned regarding the x.VXD files which "part i" below should give you some insight as to what one is, what they eventually do for a system, and how to attempt a rebuild should it become necessary. You should find as a minimum the monolithicVMM32.VXD files on your box but not the "vmouse.vxd".

PART I:

1. A Virtualization Driver (VxD) is a 32-bit protected-mode driver that manages system resources such as a hardware device or installed software so that more than one application can use a resource at the same time. VxD refers to a general virtualization driver where "x" represents the type of device driver:

a. VDD - A virtualization driver for a display

b. VTD - A virtualization driver for a printer

c. Windows dynamically loads VxDs but only those needed at any given time are loaded into memory. In addition, newly loaded VxDs do not require all their memory to be page-locked, thereby further increasing available system memory.

d. VxDs support all hardware devices including disk controllers, serial and parallel ports, keyboard and display devices, and etc.

e. While VxDs dynamically support device drivers, the virtual device keeps track of the status of the device for any application using one. Within the Windows environment, the ability to switch between multiple applications is commonplace. Each application used could interrupt the use of another by opening an application. Since an interruption can lead to problems with the use of a second application trying to access a device, the virtual device driver has the responsibility to checks and manages the states of all device applications. Furthermore, the virtual device ensures that the device is in the correct mode whenever an application continues operation after a period of inactivity. Although most virtual devices manage hardware, some such as an MS-DOS device drivers (or a TSR programs), manage only installed software and such virtual devices contain code to emulate the software or ensure that the software uses data that applies only to the currently running application. Also, VxDs are often used to improve software performance.

f. Legacy Virtualization Drivers - though non-portable, they can allow the use of legacy hardware interface. Such VxDs then acts as a "mapper" between the Windows VxD architecture and the Win32 Driver Model (WDM) architecture. For example, Joyhid.vxd forwards HID class driver information on a Vjoyd.vxd.

Note: HID = Human Interface Device classes (standard input devices, such as keyboards, mouse devices, joysticks, and game pads).

2. Supplemental reading: "Error Message: Cannot Find a Device File That May Be Needed to Run Windows (Q13200Cool."

3. The real-mode boot loader Win.com loads the monolithic file VMM32.VXD into memory during boot and then loads other dynamic virtual device driver (VxDs) files contained in the Windows\System\Vmm32 folder. Please note that any of the files in that folder, to include the Vmm32.vxd file itself, may have become corrupted and cause system anomalies.

a. Drivers contained in this files is a long list located in the system registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD

b. Additional files loaded besides those in this list are any VXD files present in the "C:\WINDOWS\SYSTEM\VMM32" folder.

c. The VMM32 program switches the computer's processor from real-mode to protected-mode and is a three-phase VxD initialization process in which the drivers are loaded according to their InitDevice name instead of the order in which they are loaded into memory. VxD loads are carried out in the following sequence, outlined and described in "Q127970":

(1) SYS_CRITICAL_INIT (SYSCRITINIT):

Interrupts are disabled during this phase. This gives VxDs time to prepare for device initialization without being interrupted by the system. No file I/O is allowed during SYSCRITINIT, so all SYSCRITINITs are not written to a Bootlog.txt file until after SYSCRITINIT is complete for all VxDs.

(2) SYS_DEVICE_INIT (DEVICEINIT):

The bulk of the VxD initialization takes place during this phase. File I/O is allowed during DEVICEINIT so each VxD's DEVICEINIT is logged as it occurs. The one exception is during Ifsmgr's DEVICEINIT. Ifsmgr takes over the real-mode file system and disk I/O is not allowed until Ifsmgr's DEVICEINIT succeeds. For this reason, Ifsmgr does not appear in the DEVICEINIT phase.

When a DevLoader VxD is called, it loads other drivers it is responsible for regardless of their InitDevice order. The DevLoader examines the Registry and finds drivers (for example, port drivers or .mpd files) and any associated support drivers and then initializes the device associated with them. During this phase if a VxD failed to initialize, or it was unable to properly communicate with a hardware device or service it, an error is renders and is typically due to incorrect hardware settings or a service was not present.

Remaining static VxDs continue the initialization phase and certain dynamic VxDs may also begin during this phase even though they do not have a SYSCRITINIT phase. In addition, dynamic VxDs may load anytime after Windows starts.

(3) SYS_INIT_COMPLETE (INITCOMPLETE):

VxDs that successfully pass the InitComplete phase should work properly. A VxD reflected in one of the previous phases which was not successfully initialized, is unloaded from memory.

(4) GUI Components:

After all static VxDs are loaded, the Krnl32.dll, Gdi.exe, User.exe, and Explorer.exe (the default Windows shell) files are loaded.

d. The WIN32.VXD file is a monolithic file (a file which can be extracted using System File Checker tool and then by reinstalling Windows so that the file is correctly rebuilt). However, this does not mean that some errant x.VXD somewhere else isn't the major culprit and is the cause of a system problem which did not get corrected through this process. I know that many users have never been able to figure this out -- including me for sometime, and was left with the option of wiping the entire system and starting from scratch. An in-depth discussion concerning the monolithic file Win32.VXD file, please read through the TechNet article "Setup Technical Discussion - Chapter Five".

e. Supplemental reading:

(1) "Invalid VxD Dynamic Link Call from... (Q137335)."

(2) "Windows 95/98 Boots Directly to "Shut Down" Screen (Q14189Cool."

(3) "Initializing Device IOS Windows Protection Error (Q263466)."

(4) "Error Message: While Initializing Device IOS an I/O Subsystem Driver Failed to Load... (Q31110Cool."

4. Use the System File Checker tool to verify the integrity of all system files. After scanning for altered files, it offers to restore corrupted files. If a file is found to be corrupt, you will be prompted to restore the original file. By clicking Settings, SFC can also be configured to notify you of changed and deleted files. If you choose to restore a file, SFC attempts to extract the file from the original Windows 98 installation source.

a. The above is what Microsoft states the System File Checker does. Please note however they do not state that it is limited to only files issued and installed by Microsoft media, since this is not true.

(1) Maybe we could say that it's lying to us but really, that utility will track other files besides. Take for instance a file which is listed as added in my SFCLOG file by the name of "Adobeweb.dll". That file is not issued with any Microsoft media that I can ascertain but had been on the system at one time and then deleted. Since it was missing on a subsequent run of the SFC tool, SFC wanted to know what I wanted to do about it. After some investigation and determining why, I updated the log to exclude it.

(2) Now that we know this we also need to know where files originate in order to extract them, right. Right? So, if a file cannot be extracted from a media for the operating system (OS), then it must come from another source, right. Right? Or else the proper path was not rendered for the media to be used.

b. The System File Checker (Sfc.exe) (Click to see an example screenshot) helps you do two things by:

(1) Scanning system files for corrupt, missing, or changed files for all major applications which have been installed on the system - not just the Windows OS. Windows-based applications commonly install shared files that may not be compatible with another application in use. You can use System File Checker to track changes to your Windows configuration and identify the affected files.

(2) Restoring original Windows 98 system files and others at the option of the user.

Note: Make note of all files that displays a dialog box requesting your action.

c. When you uninstall a program, System File Checker reports that files necessary for that program (for example, files with .exe, .dll, and .ocx extensions) has been deleted. Select #d below to update the SFC bookkeeping. Look at the dialog menu for four prompts in the section titled, What do you want to do.

Note: After installing any program, run System File Checker to determine what files dates and versions may have changed. Quickly step through the prompts and select the appropriate option to eliminate that response on subsequence runs.

(1) Update verification information - Select this option if you have deleted this file or uninstalled an application recently.

(2) Restore file - Select this option if you want to restore the file from your installation disk.

Note: If you click Extract One File From Installation Disk, you can specify the file you want to extract simply by typing the correct name and extension. Point the system to where it goes and will be extracted from by using browse.

(3) Ignore - Select this option to ignore the warning. The next time you use System File Checker you will be prompted about this file again.

=and=

(4) Update verification information for all deleted files - Select this option if you have deleted many files or an application has been uninstalled recently. Otherwise, you will be prompted to verify each individual file:

Note: Two choice are likely:

d. #2 The file it replaced is a newer file or an earlier version than the file replacing it - restore file.

=or=

e. #3 The file replaced is older as well as the version than the newer file - ignore.

Note: When #2 is selected, a context menu will prompt you for the Windows media and give you an option to indicate where this media is to be retrieved from. Normally, this is the Windows CD and the drive which designates the CD-ROM drive. Make the appropriate selection and the file will be restored to its correct default location.

f. When certain other tools in the Microsoft System Information utility have been used prior to running the SFC there are virtual device driver (.vxd) files normally updated after their use. SFC will always prompt when one of thee files are found with a newer date: Drwatson.vxd, Hwinfod.vxd, and Msisys.vxd. Simple click the option to Update verification information.

g. Installed IE v5.0 or V5.1 recently: - "Error Message: System File Checker Identified that the Following File may Be Corrupted. File: EXTRAC32.EXE (Q264865)."

WARNING: Be aware of SFC extracting the incorrect version of certain files. For example, the User.exe, GDI.EXE, Setupx.dll and/or Krnl386.exe files: - "System File Checker Tool Extracts Incorrect File Versions (Q192832)"

Hint: If you have the Windows media resident on your hard disk you may want to rename the Mini.cab in that folder to something else. At least take the b off the end the extension and you'll not forget when running SFC that an incorrect file could be extracted from it.

h. Supplemental reading:

(1) "Prompted for CD-ROM When You Run System File Checker While Correct CD-ROM Is in Drive - Q263499."

(2) "Error Message: The File Was Not Found. Verify That You Have Selected the Correct 'Restore from' Location and Try Again - Q180465."

(3) "Unable to Extract the Desk.cpl File from the Windows 98 CD-ROM - Q193312."

(4) "System File Checker", a TechNet article.

(5) "Using System File Checker", a TechNet article.

PART II:

1. The article [Q192926] discusses the Clean-boot troubleshooting process and procedure to perform a Diagnostic Startup and refers to methods of reducing behaviors that may occur because of the system's environment. Many behaviors that occur when Windows or programs run occur because there are conflicting drivers, terminate-and-stay-resident programs (TSRs), and other settings and programs that are loaded as part of the boot process and these files and programs help create the environment that is used by the operating system when the computer starts. The computer's environment includes -- but is not limited to, the settings from the following files:

Msdos.sys
Config.sys
Autoexec.bat
Winboot.ini
Windows\Winstart.bat
Windows\System.ini
Windows\Win.ini
Windows\Wininit.ini
Windows\System.dat
Windows\User.dat


2. Static VXD errors:

a. If it is suspected there is an error with a static x.VXD file, follow the above instructions and after answering Yes to Load all Windows drivers?, follow the below instructions:

b. Note each static x.VXD file loading and respond with No to avoid loading any. Below is an assumed list:

Vnetsup.vxd - Microsoft Networking
Ndis.vxd - Microsoft Networking
Ndis2sup.vxd - Microsoft Networking
Javasup.vxd - Microsoft Java
Vrtwd.386 - Clock
Vfixd.vxd - Video Phone helper
Vnetbios.vxd - Microsoft Networking
Vserver.vxd - Microsoft Networking
Vredir.vxd - Microsoft Networking
Dfs.vxd - Microsoft Networking
Ndiswan.vxd - Microsoft Networking
Msmouse.vxd - Microsoft Mouse

c. If the problem no longer occurs when responding with a No response 100%, repeat the procedure and respond with a Yes to 25% of the VXD files. Once the problem occurs, isolate that percentage where occuring and then respond to them with a Yes one at a time to identify the particular static x.VXD causing the problem.

Note: Once the responsible file is identified, delete the incompatible static x.VXD folder/file from the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD

3. CONFIG.SYS file:

a. The Config.sys file is provided for backwards compatibility with MS-DOS-based and older Windows-based programs and may not be present on your computer. It loads low-level MS-DOS-based drivers, many with a system (.sys) extension.

b. If you find an error in the Config.sys file start MSCONFIG as indicated above and click the respective tab. Remove the check mark from the box based on the notes you compiled.

Note: When you click to clear an entry in a file, a remark statement is placed at the beginning of each line. For the Config.sys and Autoexec.bat files, rem tshoot is used, followed by a space. For the System.ini and Win.ini files, tshoot is used, followed by a space. These remarks are removed when you click to select an entry that was cleared previously. When you click to select an item in the Startup tab, the registry entry is restored to its original location.

c. Depending on the type of entry you are correcting there are several things to consider:

? Is the device activation critical or can it be eliminated?

? If necessary for system operation is the error due to pathname, a corrupt or missing file?

4. AUTOEXEC.BAT file:

a. The Autoexec.bat file is also provided for backwards compatibility with MS-DOS-based and older Windows-based programs and may not be present on your computer. It loads MS-DOS-based programs, often with .com and .exe extensions.

b. ditto the procedures for Config.sys.

5. SYSTEM.INI file:

a. The System.ini file contains information about your computer's settings for specific hardware. This file must be present in the Windows folder for Windows to start. It is used to load various drivers including sound and video adapter drivers. It may also contain additional 16-bit drivers for hardware does not use 32-bit drivers.

b. Ditto the procedures for Config.sys.

6. WIN.INI file:

a. The Win.ini file contains information specific to the overall appearance of Windows. This file must be present in the Windows folder or it is re- created by Windows, is read at startup for backwards-compatibility with Windows 3.x, and many of the settings are duplicated in the registry. When you clear the Process Win.ini File check box in the System Configuration Utility, a generic version of the Win.ini file is created.

b. Ditto the procedures for Config.sys.

7. BOOTLOG.TXT file:

a. Create a Bootlog.txt (hidden file in the root of C:\). When starting the computer, use the Startup Menu to create a one-time Bootlog.txt file. Please be advised that Windows will boot much slower during the process.

Note: When examining this file in any text editor -- Notepad in Windows, or simply typing the following command at the MS-DOS prompt and then pressing Enter (clicking the icon in front of MS_DOS Prompt in the top colored bar provides MS-DOS commands), look for lines ending in LoadFailure which may indicate either a device or software problem.

b. The article [Q127970] discusses the hidden Bootlog.txt file located in the root folder, describes content, and explains certain items that may be indicated as a Load Failed which does not necessarily indicate a problem.

c. The article [Q118579] explains the root folder text file Msdos.sys set with Read-Only, System, and Hidden attributes, that this file is set to be at least 1,024 bytes in length, and describes the [Options] section that contain the settings and their meaning. Instructions are contained which allows a user to set certain options which creates the Bootlog.txt file during boot.

d. It is recommended that "Boot Log Analyser, Vision 4 Ltd" be downloaded from this link and used.

8. LAST BUT NOT LEAST: Return the "System Configuration Utility" (MSCONFIG) to Normal Startup, follow these steps:

a. On the General tab, click Normal Startup, and then click OK.

b. When you are prompted to restart the computer, click No.

9. Supplemental reading:

a. "Description of the Disk Cleanup Tool (Q186099)."

b. "Troubleshooting Windows 98 Startup Problems (Q188867)."

PART III

Testing a Real-Mode MS-DOS Mouse:

CAVEAT: The real-mode MS-DOS mouse driver must be loaded for running this test. If no configuration files are read during a boot or they do not contain the appropriate real-mode mouse driver, manually install the driver(s) from the Mouse Setup disk by typing MOUSE and then pressing ENTER at the MS-DOS prompt -- using any path necessary of where the drivers exists. If a Readme.txt file exist on the mouse, utility, motherboard driver diskette, you may want to open it by typing ''edit readme.txt'' and then pressing Enter -- there may be additional parameters required for the particular mouse used.

1. Click Start, Settings, Control Panel, System icon and then the Device Manager tab.

a. Find the peripheral in question and click the + (plus sign) before it to access sub-items. Either double-click the item, or click once and select the Properties near the bottom.

b. Check the box near the bottom labeled Disable in this hardware profile and ensure no check mark is present. If a correction was necessary, reboot the system.

2. Check the system for MS-DOS resource conflicts by using the Microsoft Diagnostics Utility (Msd.exe). If you are using Microsoft Windows 95 or Microsoft Windows 98, this utility is not installed by default. To install and utilitze:

a. Insert the Windows Installation CD-ROM into the CD-ROM drive. Press and hold down SHIFT as you insert the CD-ROM to prevent the CD-ROM from starting automatically.

b. Click Start, Find, Files Or Folders and in the Named box, type msd.exe, click Find Now or simply press Enter.

c. In the list of found files, right-click the Msd or Msd.exe file, and then click Copy.

d. Close the Find: Files Named Msd.exe window.

e. Double-click My Computer.

f. Right-click the hard disk on which Windows is installed, and then click Paste.

Note: With that exercise over with, the file MSD.EXE is located in the Win98 cabinet \tools\oldmsdos, or the Win95 cabinet other\MSD. It may be accessed directly from the CD by simply changing to the appropriate director and running the EXE file without doing anything else.

g. Shut down the computer and boot the system with a Startup disk/EBD (CD-ROM support is not necessary). Change drive designations by typing C:\ and pressing Enter. Otherwise, simply reboot the system in MS-DOS mode to the C:\ prompt:

(1) At the command prompt type MSD, and then press Enter.

(2) Tell me whether the Mouse works in real-mode (MS-DOS)?

(3) If it does not, there are hardware problems of some sort and should have nothing whatsoever to do with the mouse or Windows.

h. Supplemental reading:

(1) ''Microsoft Plug and Play Pointing Device Not Detected (Q142405).''

(2) ''Wrong Mouse Displayed in Mouse Properties (Q137801).''

Note: Do not be afraid to remove any registry entries described in Q142405. I'd also remove any listed in Device Manager as well before rebooting the computer to let Window restablish what is subsequently found.

PART IV:

As far as scanreg/restore...well the computer tells me there is no file.In safe mode I had to go to 'run' to do this...no C:.

I certainly don't understand the underlined portion but that doesn't matter right now. At your convenience, I'd like to offer the forum link "RESTORE" so you can get an education on what it is, how it operates, and why.
- Collapse -
drivers and repair guy problems...
Sep 14, 2005 9:23PM PDT

Mandy. Twice now it seems a paid repair guy messed up a PC.
A problem with updated drivers is that they become your supposed only choice when deleting device in Device Manager and "refreshing" or rebooting to reload.
You have to find the updated driver INF file in windows\inf (sometimes "other") and move it, which should leave the previous driver inf, unless the update deleted it.
Then when the device is again seen, you can choose a manual driver load and choose from the list of availible drivers already in windows.
Or you can remove the driver from add/remove, if you have that option AND you have the updated driver installation file, that you are removing, and go to www.driverguide.com and look for another or previous driver version that will work.
Up to a few years ago, updated drivers at the mfg website were about fixing problems with W98SE, ME, or other. Now they seem to focus on W2000 and XP without saying that the updated driver is NOT good for previous OS's.
And sometimes they just updated the device to sell and the updated driver is for it instead of the previous sold device.
I rarely update device drivers or BIOS unless I have a problem that I can read is addressed by the update.

- Collapse -
Cannot find it reefurbb...
Sep 15, 2005 1:02PM PDT

The folder Windows\INF or Windows\other I just cannot locate it at all.
Although the driver I downloaded is on my desktop in the folder I named downloads. It is named Aureal-8810-v312 and its path is C:WINDOWS\desktop\downloads.
When I try to update first of all the wizard tells me the file is located in C:windows\inf\other\Aureal~2.inf and I also get the same message when the wizard searches in the display a list of drivers too.It tells me the file a3d.dll cannot be found.Then I am told error code 137.
When I click on properties in my desktop\downloads Aureal-8810-v31, it tells me MSDOS name is AUREAL~1.EXE.
The list of available drivers I have are:Vortex AU8810 PCI Audio(Semi Conductor) 3-25-2002 + Vortex AU8810 PCI Audio (Semi Conductor) 4-22-1999.
I am at a loss to figure out this puzzle...hopefully it can be solved soon...Sad
In the Add/Remove program I do have listed Aureal Vortex AU8810 - that has not been there before - probably from when I downloaded.
It is difficult to find this driver on the net....when I downloaded this one I remember somewhere on the screen telling me this is an older version to the one I already have.But the year 1999 seems to be on all the files in my system...well, the ones I looked at,and in the wizard it is 2002 so that must be the one I downloaded...in my line of thinking anyway.
And no there is definately still no sound of any kind...
So I have to figure this out....should get it eventually
Hope I made sense here Happy
Mandy

- Collapse -
unhide folders-files...
Sep 15, 2005 9:46PM PDT

start-settings-folder options, I check "classic style",allow upppercase names, show all files, uncheck "hide file extensions of known types".
Open Windows folder, see inf folder, inside is "other" folder.
Your EXE download is an installation file to install the packaged audio drivers. You actually have a bunch of other audio driver files in "inf", including Aureal, but they are loaded according to the "inf" file (not folder), Aureal~2.inf is the one the PC is telling you that is now used. The ~ (enya)takes the place of more letters so that the real name is longer and there is nothing wrong with it. If you open the Aureal~2.inf with notepad or wordpad, you'll see information lines that some should list youe audio card. The PC loads all the other audio files according to this information.
You can search for the file "3d.dll" and make sure it is in the System folder.
Run the Aureal-8810-v31.exe and it should install those drivers. The listing in add\remove cannot be there unless you already installed those drivers.
As long as you have that installation file (hopefully the right one) you can uninstall thru add\remove and reinstall.
To point the Wizard, you hit "ok" until you get a dialog box that will let you hit a "browse" button, then browse for what you want.

- Collapse -
Well...not sure whats happened...followed what you...
Sep 15, 2005 11:05PM PDT

said and found the INF folder and 'other' etc.
Removed Aureal from add/remove program.
Went to desktop/downloads and clicked Aureal there to unzip.Went to add new hardware,and then update drivers in device manager although Aureal 8810 was not in there.So I rebooted and when desktop came up with only the background wizard located new hardware and installed correct Aureal 8810 with the correct drivers (Windows/Temp).Once installed and desktop done.I went to device manager and found Aureal with all the updated drivers and such...went through each one checking properties - everything looks great and correct...BUT still no sound ( also checked windows media player and put in cd...windows still cannot find the specified path and player will not let me put in Audio cd (E: ).
I am beginning to doubt if I will ever have sound now!
Bye for now
Mandy

- Collapse -
Didn't take time to read all posts in this thread.
Sep 17, 2005 12:22AM PDT

Were you ever advised to boot up in Safe Mode, go into Device Manager and remove ALL instances of the audio drivers.

Safe Mode is the only way to see if the are duplicate or multiple instances of drivers. Unless you remove ALL of them, Windows will still continue to get it wrong.

When they are ALL removed,reboot and Windows should say new hardware found. This is where you must point it to the driver that you want to use.

A Yank that met two of the three criteria. Didn't meet the "over here". LOL

- Collapse -
G'Day Yankee Ray LOL...
Sep 17, 2005 2:31PM PDT

This sound driver is giving me so much grief...ggrrr.
I have done that already....but just went back and done it again anyway after reading your message.I went to device manager in safe mode and uninstalled.
I went and rebooted and wizard came up before icons on desktop and located and installed driver (if I open the downloaded driver in my desktop/downloads folder-it unzips itself into C:\unzipped\Temp folder.BUT there are files for the driver still in C:\Temp- and they look the same).The wizard goes to the C:Temp folder.Checking device manager and driver details it is the same version I downloaded anyway.
There are more details in the threads here.
Bye for now
Mandy

- Collapse -
Let's see if I get all these posts....
Sep 17, 2005 8:20PM PDT

1. the mouse driver/problem is fixed. You edited the ini file to eliminate garbage according to M$ bulletin.
2. No onboard sound, just an Aureal sound card.
3. no sound when playing a WAV file, nor MP3 file, nor midi file.
4. you have tested speakers which are "powered types".
5. you have tried earphones in the "output" plug on the sound card.
6. your CDrom drive will show and play a data CD but not an audio CD; or it shows but does not automatically play in WMplayer nor CDplayer.exe, nor can you open the CD, see CDA files, and open with CDplayer.exe. Still no sound.
7. headphones plugged into the front of the CDrom drive does not have audio because WMplayer nor CDplayer.exe will play anything.
8. your video problem is fixed by reinstalling drivers.
9. you went to Aureal mfg web site, got latest drivers and another site for older drivers, and neither helps.
10. you have checked that the proper and complete motherboard chipset drivers are loaded.
11. you have been into BIOS-setup to make sure things seem okay.
12. you have the volume control icon in the taskbar. You have checked volume control properties to see that the Aureal is being used as "preferred device" and that volume is up to max.
13. you have checked Control Panel-Multimedia and tried checking the box for "digital audio" playback instead of "analog".
14. all the problems, including mouse-video, was working before you paid for "updates", and paid again for other service.
15. you don't want to return PC to make them fix it right because you don't want more messed up...?
Have I missed anything other than trying more advice that was posted and didn't work?

- Collapse -
Reefurbb - Stop at number 12:no speaker icon on taskbar...
Sep 17, 2005 8:35PM PDT

I did not notice this was missing-but it's not there?!
What does this mean...is it fixable simply?
No need to read any further in your post this moment!Happy
Mandy

- Collapse -
control panel-multimedia-
Sep 18, 2005 11:07PM PDT

first page (first tab), "show volume control on the taskbar", put a check in this box (1 left click of mouse arrow).
If it then doesn't show, the sound card is not installed-initiated. Back to square one about drivers.
Even tho the device shows up in Device Manager, it doesn't mean all the drivers needed are loaded.
Your next posts seem to show that no resources are allocated for Aureal 810...?
With your copy of the installation file handy, remove all the sound devices in Device Manager-Sound, Video and Game Controllers EXCEPT "wav device for voice modem". Restart PC and see if it automatically loads the sound card.