Renaming device in WinXP 64

[Dmitri]

Hello everyone,

I am having a problem with some peripheral device drivers on my Win XP 64
machine. Well, 64-bit device driver support simply sucks. In this
particular case I was able to find a driver for my Samsung SCX4100 printer
that works. The only problem is: the driver is from SCX4200. So, every
time PC boots up, it tries to install a driver for SCX4100 ('cause the
existing one shows a different name). After cancelling the driver install
for 500th time I thought maybe there is a way to rename the device (or the
driver) so the names match and the hardware installation window does not
pop up.

Anyone can give me a pointer at a resource that explains how to do that?
Is it even possible, anyways?

--

Best Regards,
Dmitri Abaimov, RCDD
http://www.cabling-design.com/
Home Cabling Guide, Cabling Forum, color codes, pinouts and other useful
resources for premises cabling users and pros

 

[Paul]

Hello everyone,

I am having a problem with some peripheral device drivers on my Win XP 64
machine. Well, 64-bit device driver support simply sucks. In this
particular case I was able to find a driver for my Samsung SCX4100 printer
that works. The only problem is: the driver is from SCX4200. So, every
time PC boots up, it tries to install a driver for SCX4100 ('cause the
existing one shows a different name). After cancelling the driver install
for 500th time I thought maybe there is a way to rename the device (or the
driver) so the names match and the hardware installation window does not
pop up.

Anyone can give me a pointer at a resource that explains how to do that?
Is it even possible, anyways?

--

Best Regards,
Dmitri Abaimov, RCDD
http://www.cabling-design.com/
Home Cabling Guide, Cabling Forum, color codes, pinouts and other useful
resources for premises cabling users and pros

For the SCX4200 driver, when you double click the installer,
it creates a folder C:\Windows\Samsung and inside there is
more than 60MB of stuff. That is more complicated than
the average driver I've played with.

Basically, the key to these is the .INF files. For example,
there is a "usbprint.inf" file, with info like

VID_04E8&PID_341b

VID is vendor_ID and PID is product_ID. The multiple lines
of values, is a listing of all the devices for which the
driver would be valid. Adding a line or modifying the values
in one of the lines, would be enough to change the list
of devices that the driver would accept.

Perhaps if you got a copy of Everest Home Edition, maybe
you could figure out the VID and PID of the SCX4100 or
whichever exact model you've got. Then, you'd have to examine
every .INF in those 60MB, and modify the files to recognize
your SCX4100. You can get Everest here, and see if it can
display any info about your printer.

http://www.majorgeeks.com/download.php?det=4181 (Everest == AIDA32)

If you can find an SCX4100 driver installer, the .INF files
in there should also have the necessary VID and PID values.

Make sure the previous driver is uninstalled first, before
modifying the Samsung folder. Double-clicking the setup.exe
at the top level, might be enough to get the installer to
run again. I did notice that the Samsung installer has an
integrity check, but I'm hoping that was for the compressed
info and it won't check to see if you have been modifying
the files

This is an awfully big driver package, to use as your first
driver hack attempt. Don't expect this to be easy.

Paul