GF3 Ti-200 vs New Drivers - FIXED!!!

Any driver above 44.xx didn't work properly on my MSI GF3 Ti-200. The problem turned out to be the BIOS (version 3.20.00.20).
I went to http://whitebunny.demon.nl/hardware/chipset_nvidia.html
and downloaded the v3.20.00.19 (3201900.rom) and NVFlash. I booted into pure DOS and flashed the BIOS:
nvflash --overridesub -f3201900.rom
Now the new drivers work perfectly.

Thx very much. It works already. I am happy. Thanks again for sharing the information

Similar Messages

New drivers don't allow anything but 2.1 speaker. (any fix for this?)

Or should I just go back to the old drivers. I may just switch brands cause i'm tired of the crackling issues on an intel chipset with no fix. Then I get new drivers and they just introduce even more problems.
So is there a fix for this or not?
This is windows vista 64 SP. Using SB fatality pro PCI-E
Message Edited by galvin on 03-3-2009 02:2 PM

Actually never installed new drivers in safemode. I used ctzapp to clean up what the uninstaller didn't get. Ran ctzapp in safe mode. then rebooted back into safemode to let ctzap finish properly. Then ran driver sweeper after all in safe mode. Its strange how creative drivers need all this work. When nvidia drivers never give problems uninstalling and installing new drivers course its for graphics but much less of a headache.
Still get static though which can't be reproduced. It just happens and when it does I can fix it without rebooting by changing the sample rate to something else then back again.

Geforce3 Incompatibility Issue with Newer Drivers

Well... now that I know that my GF3 Ti-200 won't work properly with drivers above 44.xx, does anyone know for sure if MSI is aware of this issue? Or is it all just hearsay? Are they doing anything about it? Is there a software fix or BIOS update in the works?
If MSI deviated from the reference design, they should be responsible enough to fix it.

Thaks for your message. I am having similar problem. I have the VGA card just slightly over 18 months and some of my DVDs stopeed playing. I have tried updates of drivers and BIOS, couple removals of MSI WinDVD and new installations.
NOTHING WORKS. I HAVE EVEN SEND THEM AN E-MAIL. They do not seem to give a damn.
I guess that was last time I bought anything from MSI.
George

Xfi- No new drivers? What is taking so lo

to much problems; please, i need new drivers, and new drivers for asio also. asio does not perform 0%CPU. its goes to 50%CPU and and it pops!!

i'm that kind guy that works hard to li've and gets small checks and i trusted CL, and i went to buy X-fi platinum and spent almost $200 and because i'm being using SB cards since i was a kid, i' don't know; but i had to much confidence that CL was going to fix this issues by adding new drivers, so?this is the reason that i?didn't return this product. now its being more over a year and i can't get my money back. i pay my bills and is kind of hard for me to buy stuff, so in time (a long term) i was trying to get $200 so i can by this stupid soundcard. so this is what i have now: "THE MOST POWERFULL SOUNCARD EVER!!!!!"

1212M Crackling/Popping - New Drivers

I'm kind of cranky about this problem. Read on because I actually know exactly what the problem is (at least for most of us and only Creative/EMU can fix it).
Background
I have a 1212M with the 0404 I/O card. It's a V1 that have had for five or six years. The quality of the sound is great, the features are great and the price is great. There's just one problem. From the day I got the board all those years ago I've had the crackling/popping problem that many, many other users also have.
The problem is not my motherboard, BIOS, other hardware, Windows or other applications. Over the years this EMU board has been in many different systems, many different configurations and the evolution from WinXP, Vista and now to Win7. The crackling problem has always been exactly the same. The problem is the board itself, not the system and not the configuration and I can prove it (read on).
Another thing that frustrates me is all the time that so many users have spent trying to troubleshoot this issue that is completely wasted since, for some of us, the problem is in the EMU hardware/drivers. That's not to say that there aren't some other crackling problems that are related to the system speed, interfering hardware or interfering software. There are actually two different problems that both have the same crackling symptom which makes all this quite confusing. I'll call them "System Related" and "EMU Hardware/Driver Related". If you're having the crackling symptom you should figure out which type of problem you have before spending hours troubleshooting, reinstalling, etc, etc, etc. Here's how:
If your crackling problem:
- Doesn't happen on startup. Your audio is fine and the problem only develops after a while. On my system it's between 60 and 90 minutes and resetting the card.
- Starts with a few minor crackle/pops per second and gradually gets progressively worse over several minutes with nothing else changing in the system (ie not running new software or changing anything).
- After a while (can be a long while) the crackling can actually go away again and you have clean audio. Then the crackling returns. Once again with no changes in system load in between.
- You can make the crackling go away instantly and every time by simply resetting the clock on the card. There are several ways to do this. In Patchmix go to the System tab under Session Settings and switch the clock between internal/external (whatever you have it on, go to the other and back again). Another way is the change the ASIO Buffer Latency milliseconds in your host software's ASIO control panel.
If those four things are all true for you then you have the "EMU Hardware/Driver Related" type of crackling problem. Do not waste any time with all the well-meaning but misguided troubleshooting ideas posted on this and other forums. None of it will help.
If these four things aren't true on your system then by all means you should try all the troubleshooting steps because it's likely that you can resolve your crackling problem.
Here is what is happening with the "EMU Hardware/Driver Related" type of crackling problem. First, let me say that I know what the root of the problem is because I used to work for a company that developed high-end professional video/audio software for Windows PCs. We encountered this exact same problem when some our users started reporting it. It wasn't solely with Creative or EMU hardware because the problem can actually happen on a variety of PC audio cards where the hardware is slightly out of spec or malfunctioning and the software driver is not capable of correcting the problem.
Our most senior software engineers banged their heads against this problem for quite a while until they determined what was going wrong in our customer's PC audio hardware. The issue is that the clock on the card is drifting slightly which means it is going a little faster or slower than the current sample rate. That's why the problem only manifests after a while. It's also why the crackling goes away when you reset the clock. The fundamental issue is that the audio data coming from your PC is being written into a buffer. The data is written by the PC driver and read from the buffer by the card and then sent to the card's output. You can think of the buffer as a big circle of memory. There's a write pointer that writes one value of data and then increments one step and "180 degrees" opposite in the circle of memory is a read pointer that reads one value of data and then increments one step.
These two pointers never move at exactly the same speed. They are constantly slowing down or speeding up a little bit but over time on average they end up advancing at about the same rate. The problem is that when the clock on the card is drifting, the read pointer and write pointer will eventually cross over. That's why the this kind of crackling problem manifests only after a while because, depending on the drifting, it takes a while for the pointers to cross. It's also why the crackling is subtle at first and then gets progressively worse over time. Right when the pointers are overlapping the timing is still close. As one pointer starts to "lap" the other point more and more the crackling artifact gets progressively worse. That's also why the problem usually goes away again if you wait long enough. The pointers can actually get back in phase again for a short while! That's how I know exactly what the current problem is the 1212M board because it manifests with these precise characteristics. The old problem my former companies user's had even sounded exactly the same as the crackling my EMU 1212M has.
Once we understood the problem, in our next version we modified our software to use a larger buffer. This eliminated the problem for some of our customers whose hardware clock was only very slightly out spec. However, for other customers the problem remained, although by increasing the buffer size it made it take longer for the pointers to reach each other and the crackling to begin. This is the what I suspect EMU has done with the new Win7 beta drivers. With the new drivers my crackling takes longer to appear. In these forums we see reports from some long-time sufferers of the problem that the new driver fixed their problem and from others we hear that they are still having the problem.
Since we still had unhappy users of our video/audio application software, we kept working on the issue and eventually came up with a fix that solved the problem for all users and all audio hardware. It was hard to implement but this is what EMU/Creative needs to have their driver engineers do to actually fix the problem (short of replacing an enormous amount of hardware).
The problem can be solved in the driver (yes, my old company actually embedded our own low level generic driver in our application software). Since EMU/Creative is making their driver themselves they can just implement this fix there. The secret is for the driver to actually keep track of where the write and read pointers are and each time they get too close to each other it stretches or shrinks the next packet of data by averaging the audio samples in that packet to the exact size needed to put the pointers 180 degrees apart again. It then resets the pointers as it writes that new data. The data shrink or stretch prevents a single pop or click from happening when the pointers are reset to their correct positions. Frankly, this was hard to implement but it worked perfectly. We actually hired a consultant to figure this audio problem out who was a former Microsoft engineer who wrote the WDM kernal mode drivers.
EMU SUPPORT please let your product manager know that this is what is going on and that he should ask your contract driver engineers to implement this type of solution. Yes, it will cost more in development time (and hence $$$), but it will fix the issue once and for all and not just for this card. You can re-use the code in other drivers.
If you need specific help, I'll even connect you with the engineers that did it for a more detailed explanation (we sold our company years ago and the team has split up but I'm still in contact with most of them).

Markran,
Thank you for the information. I will make sure that it gets routed to the correct people.
Casey

Has there been any new drivers or patches for kensington trackball expert using mountain lion?

are there new drivers or patches for the kensington trackball expert? i'm using mountain lion on the imac 3.06 ghz intel i3 and it will not recogmize any driver i install. all this after the installation of mountain lion.

Kensington has a new version of Trackball Works 1.1.1 available, try it and see if your problems go away.
It is made for Lion & Mountain Lion.
TrackballWorks for Mac v1.1.1
March 11, 2013
Welcome to version 1.1.1 of TrackballWorks for Mac. This document describes the latest changes.
Compatibility
Mac OS X 10.8 Mountain Lion
Mac OS X 10.7 Lion
Mac OS X 10.6 Snow Leopard
Supported Hardware
SlimBlade™ Trackball (K72327)
Expert Mouse® (K64325)
Orbit™ Wireless Mobile Trackball (K72352)
Orbit™Trackball with Scroll Ring (K72337)
Orbit™ Optical Trackball (K64327)
Installation Instructions
To run the installer, double-click on the DMG file, then double-click on"Kensington TrackballWorks.pkg". Follow the on-screen instructions.
Fixes Issues
Resolves an installation problem with Mountain Lion where TrackballWorks may not install properly with the Mountain Lion default security settings.
Resolves an issue with settings persistence where, after a reboot, some settings become reset to their defaults.
Changes & New Features
Button actions that are dependent on the Mac OS X version now correctly display or hide depending on the version of Mac OS X being used.
Button action "Launchpad" has been added for Mountain Lion.

New Drivers ,When ???

[ALIGN=center][size=15]
New Drivers ,When ??? [/SIZE] [/ALIGN]

From the Audio Driver Problem thread:
Quote
Posted: Sat Oct 19, 2002 3:13 pm Post subject:
I talked to NVIDIA about the BSOD on nForce 1 and they have a driver that fixes that. We should be seeing that driver soon.
by guy at http://www.bjorn3d.com/

Will there be new drivers this ye

Hi everybody!
My System Specs: Athlon XP 2400+, GB DDR400, Radeon 9800 Pro, Audigy 2 ZS, Win XP
I have tried (for several hours) to record or using timeshifting in my Pinnacle PCTV Vision software...
Didn't work without manual settings in the mixer.
Then I have tried a solution for that...
And found this:
The problem is simple: To record analog audio with an Audigy, you need to record from the "Analog Mix" line, which mixes the several analog sources together. What makes the problem REALLY serious is that it does NOT record from a source which is muted. Since all timeshifters mute the line they record from (in order to not have repeated sound, one coming from the line and one timeshifted), Audigy does NOT record the audio. In order to get what is needed for timeshifting, the line has to be not muted, and a setting called "Record without monitoring" of the Analog Mix line has to be turned on. Really ugly issue! If the timeshifting program does not have specilized code to handle Audigy correctly, there is almost nothing you can do. There is an ugly workaround: choose a WRONG line in the timeshifter (eg. CD instead of Line-in/Aux), use your mixer to MANUALLY turn Line in/Aux on and find the "Record without monitoring" flag and turn it on. Timeshifting should work, but the program will no longer turn the sound from the channel on or off: you'll get background noise in your computer especially when you're not using the tuner, and you'll probably get noise when switching channels. BUT if your timeshifter monitors the audio line for some reason (e.g. Pinnacle's Vision does it) you won't get any sound with non-timeshifted playback. 

So I posted this information to the Pinnacle Support forum and got that answer:
That is a well known problem and the company is working on new drivers at the moment - but it is not known when these drivers will be published by the soundcard manufacturer. So there's no ther solution than waiting, sorry.

So...will these new drivers will be released soon?
I think every Audigy user is waiting for that one. Maybe it is published this month, because new drivers seem to come
every March and November each year...

I also have the problem with Pinnacle PCTV/Audigy 2, reported by numerous users both in SB and Pinnacle forums. (The problem in short, is that if Timeshifting is enabled in PCTV Vision, the line-in is muted when recording, resulting in silent recordings. Effecti'vely, this means the timeshifting feature does not work with Audigy 2) I have an on-going support case with Pinnacle, but they do not seem to acknowledge the problem; they just go on about updating drivers and re-installing the software. Clearly, the problem is a quirk with Audigy 2 that PCTV does not handle. So who to blame? To add to my frustration, I discovered that my Audigy 2 is a Dell OEM version, so even if Creative were to fix this, I would have to wait for a Dell specific version of the driver. Sorry for all the negativism, but I needed to vent...
On the positi've side, I did discover a work-around that actually seems to work. I can enable the integrated sound on the mother board, connect the PCTV card to the integrated line-in and the head phone jack to the Audigy 2 line-in. Then configure PCTV to record sound from the integrated sound. This is not ideal, but again, it works

Are X-F1 new drivers installable over beta

Installed the 5/30/06 Betas that said they were good until September 06 when they safely could be replaced. The new driver set including the beta changes is now available. Is there any problem installing these new drivers over the Betas??Message Edited by dogin on 08-02-2006 06:35 AM

Well I took the plunge last night and reverted my system back from SP1. Uninstalled the drivers and software and then reinstalled them with no SP1 installed. And still no WinDVR working. :
[ranrt]
I do think however anyone who is having issues with the winDVR software and XP SP1 should send MSI tech support an email because I think it is unlikely they have the time to surf the forum for complaints. So if we want to get anything done about the SP1 issues, we're going to need to send them emails. But please send professional civil emails, if they get bombarded with angry swearing emails I think they're not going to be in a real big hurry to fix things.
[/rant]

What About New Drivers Creative.

there is a lot of complain about the drivers of the audigy2 zs sound card and creative seems to ignore them from what I hear the drivers of the audigy4 is a lot batter and fix most of the problem that the audigy 2 zs have it's look like creative is making new drivers every 6 month so please don't forget your "old" customers and start give as some support and release new drivers for "old models" like the audigy 2 sz...!

I'm guessing you should still be able to keep your current plan. The only thing really being phased out is unlimited data for existing customers. The link below has a table on the 2nd page for the Share Everything plans that apply to basic phones.
http://solutions.vzwshop.com/shareeverything/pdf/verizon_share_everything_plan_details.pdf

New drivers to be available so

According to this press release, Sound Blaster cards will receive support for OpenAL . API. I think it means newer drivers will be available for the X-Fi and perhaps Audigy family that have OpenAL . support.

where did u see that the new drivers will fix pops/crackles? u assume?
CL is still investigating it... lol

Tried to update iPod, failed, no new drivers installed. Now iPod does not show in my computer or in iTunes.

Anyone know how I can update/unbrick this iPod? It's useless. It's stuck on the screen that says connect to iTunes. iTunes doesn't know it's there. My computer doesn't know it's there. It's not the USB port.
Please don't direct me here - http://support.apple.com/kb/HT1808 - already tried, no results.
Last time it was a missing driver for iTunes but iTunes says nothing new is needed. Help appreciated.

Let me try this again. My computer said my iPod needed an update. I clicked ok. iTunes said it was doing the update. I browsed the internet. I came back to it after it was done, and it said update failed, no new drivers installed. Now my iPod touch is a brick. I cannot use it for anything. You know that screen that shows the usb cable, a white arrow, and iTunes? It's stuck there. No amount of pushing the sleep/wake button and home button will convince it to go to any other screen. When I go to 'My Computer', it does not recognize that there is anything there. It is not the USB port. Everything was fine until the update tried and failed.
I am not installing iTunes (piece of crap software that it is) on the other computer in my apartment.
I have exhausted the articles that sort of go with the problems I am having. They all assume a non brick iPod. Mine is a brick and therefore those articles, including the one you linked, are not relevant.
Not meaning to be rude, but I came into this not caring much for Apple's business model. I've had my iPod for .. a week? Maybe two, and nothing I've seen has convinced me to feel otherwise. Apple's products are supposed to just work. I am not finding that to be the case. Anyone with anything helpful please?

Hi can anyone help me. I have a apple macbook laptop OSX 10.5.8 . When i push print, it shows my printer but says cannot communicate with printer. (epson stylus nx125). Do I need new drivers? Please help . regards Cindy

Hi can anyone help me. I have a apple macbook laptop OSX 10.5.8 . When i push print, it shows my printer but says cannot communicate with printer. (epson stylus nx125). Do I need new drivers? Please help . regards Cindy

Welcome to Apple Support Communities. We're users here and do not speak for "Apple Inc."
Some basic printer troubleshooting steps before worrying about a printer driver:
1. Have you tried turning the printer off and back on?
2A. Is the printer attached with a cable?
     If yes, have you tried unplugging and re-plugging both ends of the printer cable?
     If that does not help, can you test the printer with another cable?
2B. If your printer is not connected to the computer with a cable, have you tried restarting your printer (assuming wireless connection)?
     Have you tried restarting your wireless router?
3. Have you tried restarting your MacBook? (Be sure to save your work first.)
4. Does the printer have ink? (Doesn't usually generate a 'communications error' though)
5. Have you updated OS X or the program you're trying to print from recently?

New drivers won't work for X-Fi Xtreme Gamer

I use Windows XP SP 2 with my X-Fi Xtreme Gamer.
I used the Device Manager to uninstall my old drivers (v2.5.0006), rebooted, cancelled the Windows new-hardware popup, and installed the new drivers (v2.5.0008). I had no sound immediately after the installation, though I think I should have heard mouse-clicking sounds and sounds that accompany opening and closing windows from my desktop and Windows Explorer. After restarting after the installation, I still had no sound.
To restore sound, I uninstalled the new drivers and reinstalled the old ones.
Has anyone else encountered this trouble Does anyone know what is happening
Here is some information on my system:
Operating System: Microsoft Windows XP Home Edition
Version: 5..2600 Service Pack 2 Build 2600
System Name: YOUR-C7B5E9C69F
User Name: YOUR-C7B5E9C69F\Russell
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume
Locale: United States
Hardware Abstraction Layer Version = "5..2600.280 (xpsp_sp2_rtm.040803-258)"
Time Zone: Pacific Standard Time
System Manufacturer: Magnell
System Model: ABS Ultimate M6
System Type: X86-based PC
Motherboard: ASUS A8N-SLI Deluxe NF4 (Socket 939)
Processor: x86 Family 5 Model 7 Stepping 0 Authentic AMD ~263 MHz (AMD Athlon 64 FX-55 (2.63 GHz), socket 939
BIOS Version/Date: Phoenix Technologies, LTD ASUS A8N-SLI DELUXE ACPI BIOS Revision 006, 3/3/2005
SMBIOS Version: 2.3
Memory: Dual DDR GB PC3200XL Corsair
Total Physical Memory: 2,048.00 MB
Available Physical Memory: .68 GB
Total Virtual Memory: 2.00 GB
Available Virtual Memory: .96 GB
Page File Space: 3.85 GB
Page File: C:\pagefile.sys
Video: EVGA NVidia GeForce 6800Ultra 256MB
Video Card Drivers: NVidia Forceware drivers version 6.4.00.756
Hard Dri've: Western Digital Raptor 74GB WD740GD 0,000RPM 8MB
Sound: Creative Labs Soundblaster X-Fi Xtreme Gamer (driver v2.5.0006)
CompUSA Dual Format Double Layer DVD+/-RW USB (R = 6x DVD, 48x CD)
Monitor: Samsung SyncMaster 93c 9 LCD
Mouse: Logitech G9 Laser (Driver v.4.22.52)
Keyboard: Ideazon MERC Stealth Illuminated Gaming Keyboard (Model No. KUH0702)
Printer: HP Photosmart C5580
Mass Storage Device: Corsair Flash Voyager 2.0 GB (USB 2.0 flash memory dri've)
Power: PC Power and Cooling Turbo-Cool 50
Email: Outlook Express version 6.00.2900.280 (xpsp_sp2_rtm.040803-258)
Virus and Spyware Protection: Norton Internet Security 2009
Internet Service Provider: SBC/Yahoo! Pro DSL

I have solved my own problem. The trouble was that using the Device Manager to uninstall my old drivers did not work. Apparently a file that needed to be deleted was not deleted, and that file prevented the new drivers from working. I finally got the new drivers to work by using the following procedure, which except from some notes I have inserted, was obtained by email from Creative support:
1. Go to Control Panel, Add Remove Programs and un-install all listings related to your audio card. Do not restart your computer when prompted so.
2. Go to Control Panel, and switch to Classic View. Click System, Hardware tab, Device Manager button and delete all sound cards entries in Sound, Video and Game Controllers as well as any previous sound card entries from the Device Manager. ?Note: Personally, to get to Device Manager, I don?t follow these directions. I do this: click the Windows Start button + E, look to the left and right-click My Computer, click Properties, click Hardware tab, click Device Manager.
3. Reboot the computer and cancel out of any driver installation if you are prompted. Insert the Creative Sound Blaster installation CD into your CD-ROM dri've. Exit from the installation wizard if it autoruns.
4. Click Start, Run and then Browse. Browse to Z:\Audio\Drivers\CTZAPXX.EXE, where Z represents the CD Rom Dri've. Choose YES if you receive a prompt "Overwrite existing shared creative audio driver files?" NOTE: This CTZAPXX.EXE file could not be found on my X-Fi Xtreme installation disk by using the Z:\Audio\Drivers\CTZAPXX.EXE path. I had do use the Windows Search engine to do a search on my X-Fi Xtreme installation disk. After finding it, I highlighted the CTZAPXX.EXE program, opened it, and continued with these driver-uninstallation instructions. This seems to be a critical step. If your installation disk doesn't have this file, or if you don't have an installation disk, I suggest doing a Web search for CTZAPXX.EXE. It's a Creative Update Utility, so I don't think it will harm your computer. But I use Windows XP, and I don't know anything about Vista.
5. Select Driver un-installation for WDM drivers and click OK.
6. When prompted to restart, say No.
7. Click Start, Run, type MSCONFIG and press Enter.
8. Check the box next to Selecti've Startup and deselect Load Startup Items.
9. Select the SERVICES tab and select Hide All Microsoft Services.
10. Uncheck all results and click OK.
1. Browse to the C:\Temp folder and C:\Windows\TEMP (if it exists) - all files and folders in the temp folder need to be either deleted or moved to a new folder. ?NOTE: I had to go to my C:\Windows\TEMP file to do this step. Also, I took care to copy and paste all of these TEMP files to a new folder before I tried deleting them. Then I deleted all the Windows\TEMP files that I could. Some would not delete. Indeed some of these files could not be copy and pasted to the new folder. But that was okay. I just left alone those files I could not copy and delete, and I proceeded to delete all of the other files. The TEMP files that I could not delete did not affect my uninstallation of old sound drivers or the installation of new sound drivers.
2. Browse to Program Files, Creative and delete the Sound Blaster Folder - if you get a file that won't delete, right click on the file, click Properties and clear all the attributes. The file should then be able to be deleted.
3. Empty the Recycle Bin, and reboot the computer.
4. If you wish to install your new sound drivers, do so now. Otherwise, go to the next step. If you do install you new drivers?which I would do?don?t restart after the installation. Do the next two steps first.
5. Click on Start, Run. Type MSCONFIG and press Enter.
6. Select Normal Startup, and press the OK button.
7. Reboot the computer
8. At this point I copy-pasted all those Windows\TEMP files from my new folder back to their proper place in Windows\TEMP. Then I deleted the new folder. While restoring these TEMP files to the Windows\TEMP file, I got a couple of messages telling me these files already existed. I clicked No. That is, I did NOT replace or overwrite any existing files in the Windows\TEMP folder.
9. The new sound drivers should now be working.
Message Edited by Solipso on 04-22-2009 07:6 AMMessage Edited by Solipso on 04-22-2009 07:7 AM

"Extraction Failed: Cannot Open Output File" error message when installing new drivers

Hello, I'm trying to install new drivers for my HP Photosmart C4385 Printer. I downloaded the full feature drivers for Windows XP 32-bit, and when I start to install (extract), I get the error message:
Extraction Failed
Cannot Open Output File
And the process closes. It happens at about 85% extraction every time.
Any idea why? I called HP but since it is out of warranty they wanted money, which I think as absolutely ridiculous - won't even give me basic support?? Poor, poor customer service.
This question was solved.
View Solution.

Hi,
If you haven't still got the Full Feature software installer, download it from the link below and save it to your Desktop. If you already have it, place it on your Desktop.
ftp://ftp.hp.com/pub/softlib/software10/COL20274/mp-53147-4/100_228_PS_AIO_02_Full_USW_enu_NB.exe
Make sure the Printer is disconnected from your PC.
Download and install 7-ZIP. Once installed, right click on the software installer for your printer, select 7-Zip and choose extract files, then click Ok.
Open the newly extracted folder and double click the setup application to start the installation ( the setup application will probably have the same icon as the original software installer you downloaded ). Connect the printer to your PC when the software asks.
Hope this helps.
Best wishes,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

GF3 Ti-200 vs New Drivers - FIXED!!!

Similar Messages

Maybe you are looking for