windows xp installs my h470 officejet printer as a disk drive

Mar 17, 2018
21
0
10
0

yes installed the hp software and driver when it asked for the printer to be plug in to the usb port I did so then a message
comes up found new hardware and installs the printer as a removable disk drive and the hp software also installs it as a printer
 
Mar 17, 2018
21
0
10
0
no because the programme I want to use with the printer the programme it recognises the printer and when you print
a page a message comes on screen saying printing and no page is printed
I installed another printer and this printer works with the programme so what is going on
 

COLGeek

Titan
Moderator
Can you print a test page from the offending printer?

Printing A Windows Test Page Using Windows XP

Click on the Windows Start Button.
Select Control Panel.
Double-click Printers and Faxes.
Right-click the printer, then click Properties.
Click Print a Test Page.
After the Test Page has printed, click OK.
 
Mar 17, 2018
21
0
10
0
yes I can the problem is the software I want to use to print from the software when you select print a message comes on
screen saying printing but the printer does not print there seams to be no signal going to the printer from the software
 
Mar 17, 2018
21
0
10
0
the software is a automotive diagnostic software
I tried another hp printer a hp deskjet f 2180 and installed as per instructions and this printer did not work either
the software and driver for both printers were down loaded from the internet using my windows 7 home computer
then I burned the hp software to disk as my dell laptop is not set up to go on the internet
I also installed my pantum printer on my dell laptop which I do have an original software disk and this printer worked
with my automotive diagnostic software so I can only come to the conclusion that the hp software is at fault what do you
think
 
Mar 17, 2018
21
0
10
0
I installed the h470 driver and software on to my Toshiba laptop and the same thing happened both laptops are running
xp professional so I think that that xp professional is the problem so is there a difference between xp home and xp pro
 
Mar 17, 2018
21
0
10
0
it is connected to my dell latitude d600 via a usb cable and the diagnostic equipment is a mg rover t4 testbook original
made by hp for mg rover so the software is written to work with hp printers so I think that xp pro is the problem

 

COLGeek

Titan
Moderator
I'll pass this thread to the moderation team to see if anyone else has a clue. Seems the application should use whatever the default printer in Windows is. I know of no reason why XP Pro should be an issue.
 
Mar 17, 2018
21
0
10
0
I may have solved the problem I connected a usb 2.0 hub to the usb port on the laptop hardware wizard found that new hardware has been connected and installed then I connected the printer usb cable to the usb hub to see what would happen nothing did so hardware wizard did not detect it so now I need to install the printer software and diagnostic software I will let you know the result
 
Mar 17, 2018
21
0
10
0
tried the above but it did not work so I googled how to disable hardware wizard and found this
http://www.computertechblog.com/how-to-disable-the-found-new-hardware-wizard-in-windows-xp/
there was some instructions there as follows
Windows XP 32-bit and Windows Server 2003
Add a DWORD named SuppressNewHWUI with a value of 1 to the below key:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\DeviceInstall\Settings
DeviceInstall and Settings keys may not exist, you will have to create them

Windows XP 64-bit and Windows Server 2003
Add a DWORD named SuppressUI with a value of 1 to the below key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PlugPlay\Parametes
my question is how do you create deviceinstall and settings keys in regedit
 

ex_bubblehead

Glorious
Moderator
Do NOT go playing around with PnP things you do not understand. You will only create problems that may require reimaging to reverse.

If the printer prints a test page from the printer control panel then Windows is not the problem, the problem lies with the application. One question that hasn't been asked/answered is, is this printer specifically called out in the software's documentation as compatible?

The application may well not be sending the proper "end of page/document" token for this printer and the driver is left waiting.

Another question: Is this Windows XP 32-bit or 64-bit? Everything I've seen so far states that drivers are only available for XP 64-bit. 32-bit is never mentioned.
 
Mar 17, 2018
21
0
10
0
thank you for your help and reply
my laptop is a dell latitude d600 with windows xp pro os system I don't know if it 32 bit or 64 bit
first I installed the h470 software then when asked I plug the h470 printer into the usb port after the software has
installed I go to start printers select printers the window opens and the hp officejet h470 series is there and displays
ready I go out of this window and selest my computer in this window I shows a removable disk d next I go to my computer
and right click the mouse button on manage then I select device manager in the next window select disk drives and thehp officejet h470 usb device has been installed there then I go to universal serial bus contrllers and it shows that the printer has been installed here as officejet h470(dot4usb)
the diagnostic software I want to use to print fault codes sends the pages to the removable disk how can I sort this out is it possible to post a photo of the device manager window for me to show where the 2 locations the
printer has been installed I am sure this is the problem and once sorted the printer will work with the software
I understand that changing settings in the registry is not for the amateur computer buff but is it possible to disable the hardware wizard
 
Mar 17, 2018
21
0
10
0
what? documentation, for that specific piece of software, to see how to change the default printer. do you mean this type of documentation

;=========================================================================
;
; +--------------------------------------------------------------------+
; | Copyright Hewlett-Packard Co. 1993 |
; | All Rights Reserved |
; +--------------------------------------------------------------------+
; | Copyright Omitec INformation Services Ltd Co. 2002 |
; | All Rights Reserved |
; +--------------------------------------------------------------------+
; | Reproduction, adaptation, or translation without prior written |
; | permission is prohibited, except as allowed under copyright laws. |
; +--------------------------------------------------------------------+
;
; FILE NAME: RDS.INI
; ~~~~~~~~~
;
; DESCRIPTION
; ~~~~~~~~~~~
; This file contains Windows profile information unique to RDS.
;
; HISTORY
; ~~~~~~~
; $Log: //omitec-cov1/rds/DISCUS31/RDS/COMMON/RDSINC/RDS.INV $
;
; Rev 3.50 Jan 20 2004 17:28:22 lawtonm
; RDS 5.06 - Also added new VIN validation to cover City Rover
;
; Rev 3.49 Nov 17 2003 09:38:18 lawtonm
; RDS 5.05 Release
;
; Rev 3.48 Sep 10 2003 17:57:48 x_pughk
; RDS 5.04 pre-release ...
;
; Rev 3.48 Sep 09 2003 17:56:48 x_pughk
; Rds 5.04 pre-release
;
; Rev 3.47 Jun 24 2003 12:46:40 x_pughk
; 5.03 base line build ...
;
; Rev 3.46 May 20 2003 16:50:40 x_pughk
; Latest tweaks for rds.ini ...
;
; Rev 3.45 02 Apr 2003 17:51:50 x_pughk
; CBT using Exe and Dir path in rds.ini and ...
; addition of Comms Layer entry in rds.ini
;
; Rev 3.44 12 Mar 2003 12:28:52 x_pughk
; Number of braod changes to make file more user friendly.
;
;=========================================================================

[RDS]
WinErr=ON
hosted=no
RemoteHostname=discus
LocalHostname=RDSHost
BySystemMap=D?00?SY?.SS
BasicToolboxMap=basic.sb
; BasicToolboxMap=test.ss
; BasicToolboxMap=mark.ss
XTBAuthSet=SetXTB.sx
XTBAuthMap=xtbauth.sx
XTBMap=D?00?XT?.SX
XTBPassword=na
RVA=no
display=white
GrayMode=UseColor
ConfigPassword=
ButtonDelay=200
InstallType=4
[end_RDS]

;=========================================================================
; [ProcessManager]
;
; ShowWindow
; Determines initial application display state. Passed to application
; as nCmdShow parameter to WinMain. Values equate to SW_* values in
; windows.h.
; ShowSysMgr
; Determines display state for System Manager, similar to ShowWindow
; parameter above. Values equate to SW_* values in windows.h. Default
; value is SW_HIDE (0).
; ShowOthers
; Determines display state for non-RDS applications, such as Program
; Manager, similar to ShowWindow parameter above. Values equate to
; SW_* values in windows.h. Default value is SW_HIDE (0).
; Shutdown
; Determines extent of shutdown request and to be used for development
; purposes only. When equal to "no", a shutdown request will exit to
; RDS, leaving Windows running. An undefined value or not equal to "no",
; a shutdown request will be honored. The request will either:
; 1) Exit to DOS, or
; 2) Reboot system, or
; 3) Restart Windows and RDS
; The default value is "yes". The shutdown request issued by Welcome
; screen causes exit to DOS.
; T4Shutdown
; Determines shutdown of T4 machine via the T4Menu exe
; StartUp
; Blank-separated list of Process Manager applications to start when
; RDS is started. For example, netcom, Welcome and DocDB in a hosted
; configuration, or Welcome and DocDB in a standalone configuration.
; If not defined or blank, then no additional apps are started.
; welcome, se, tis, netcom, ...
; Defines pathname of application executable and static parameters.
;
;=========================================================================
[ProcessManager]
ShowWindow=0
ShowSysMgr=0
ShowOthers=0
Shutdown=no
T4Shutdown=no
StartUp=welcome
welcome=c:\rds\bin\welcome
se=c:\rds\bin\se
tis=c:\rds\bin\tisexe
bjc=c:\rds\bin\bjc
docdb=c:\rds\bin\docdbsvr
CD_Update=Z:\fupdate\update
rit=c:\rds\bin\srit0100
HelpPath=C:\RDS\HELP
[end_ProcessManager]

;=========================================================================
; [LogHandler]
;
; fmt*log
; File name for formatted log file
; raw*log
; File name for raw log file
; *target
; Set of bit flags that control disposition of log entries.
; 0x01=log in raw file (defined by *rawlog values).
; 0x02=log in formatted file (defined by *fmtlog values).
; max*logsize
; Defines the maximum size of a log in KB.
; syslevel
; Initial system log level.
; msgdll
; Name of the stringtable DLL that contains log template strings.
; *wrapsave
; Most recent KB of log file to keep when wrapping log file. Value
; applies to both raw and formatted versions of a given log type.
; vehhostdir
; Unix-style directory path on host where vehicle log files are stored.
; Trailing '/' is not required.
; vehlocaldir
; DOS-style directory path on RTB where vehicle log files are stored.
; Trailing '\' is not required.
; extlogging
; Set to 'yes' or 'no'. Currently only used by DocObject to en/disable
; logging of its internal data structures to the system log file
; for verification purposes
;
;=========================================================================
[LogHandler]
rawsystemlog=c:\rds\rawsys.log
fmtsystemlog=c:\rds\fmtsys.log
syslevel=1
systarget=2
maxsyslogsize=10
syswrapsave=2
syshostdir=/tmp
msgdll=logmsg.dll
rawerrorlog=c:\rds\rawerror.log
fmterrorlog=c:\rds\fmterror.log
errtarget=2
maxerrlogsize=10
errwrapsave=2
errhostdir=/tmp
vehhostdir=/tmp
vehlocaldir=c:\rds
vehtarget=3
maxvehlogsize=1000
vehwrapsave=0
extlogging=yes
Log=1
Editor=Notepad.Exe
[end_LogHandler]

;=========================================================================
; [Print]
;
; spooldir
; Location of print spool files
; printer
; Either 'local' or 'remote', defines destination of spool files
; hostdir
; Host directory to where files are transferred for host printing
;
;=========================================================================
[Print]
spooldir=c:\rds
; printer=local
printer=remote
hostdir=/tmp
[end_Print]

;=========================================================================
; [TacticFastPrint]
; YES - Any non-zero value,
; NO - Omission or zero.
;
;=========================================================================
[TacticFastPrint]
HP DeskJet 720C Series=1
HP LaserJet 6P/6MP=0
HP DeskJet 400 Printer=1
HP DeskJet 300 Series=0
[end_TacticFastPrint]

;
;=========================================================================
; [docdb]
; DocDBMode=0 -> (CD-ROM)
; DocDBMode=1 -> (TOC browsing allowed, hard disk RTF/TIFF files)
; DocDBMode=2 -> (no TOC browsing, hard disk RTF/TIFF files)
; DocDBMode=3 -> (CD image on hard disk)
;
; DocDBHDPath
; Specifies the path of the root directory where DocDB hard disk files
; are stored. Specifically, the CD release files are copied from CD onto
; hard disk based upon the value of this keyword. Path should use Unix
; type slashes and be terminated with a /.
;
; DocDBPath
; When a document is requested, DocDB always returns the full path to the
; file which the caller may then use to access the document.
; Depending on the mode, DocDB either retrieves
; the file from the database and deposits it in the specified directory,
; or just prepends the path and returns the fully specified DFN.
; Path may be specified with either DOS or UNIX style separators (\ or /)
; and must be terminated with a slash unless it's left blank.
; DocDBMode 0 or 3:
; Specifies the destination directory for files retrieved from the
; database. If path is left blank or ./ is used, the current working
; directory will be used.
; DocDBMode 1 or 2:
; Prepends the specified path to a DFN. The database is not accessed.
; This allows the calling application to bypass the database and use
; it's own datafiles.
;
; DocDBTOCPath
; For all DocDBModes, specifies the directory of the root of the
; Table Of Contents (TOCs), and indexes, on CD.
; Note that forward slashes are used, and the specified path must be
; terminated with a /. This is required by the Infobase libraries,
; and cannot be changed.
;
; DocDBUPDPath
; Specifies the path where updates are installed.
; Path should use Unix type slashes and be terminated with a /.
;
; DocDBCD
; Specifies the logical CD-ROM drive or harddisk path depending on
; DocDBMode. Path should use Unix type slashes and be terminated with
; a /.
;
; DocDBMap
; Specifies the full DOS pathname of the toc.map file which contains the
; cross-reference mappings between MAKE/LANGUAGE and High-Level TOC.
;
; DocDBReleaseFilename
; Specifies the name of the release file. This file is always located
; at the root level of a CD. Don't prefix a path.
;
;=========================================================================
[DocDb]
DocDBMode=0
DocDBHDPath=C:/RDS/DOCDB/
DocDBPath=C:/RDS/DOCDB/
DocDBTOCPath=Z:/
DocDBUPDPath=C:/RDS/DOCDB/UPDATE/
DocDBCD=Z:/
DocDBMap=C:\RDS\DOCDB\TOC.MAP
DocDBReleaseFilename=RELEASE.TXT
DocDBRaveFilename=CD.INI
LockCD=YES
[end_DocDb]

;=========================================================================
; [ViewDoc]
; StartPath
; Specifies the directory viewdoc lists initially.
; The path must be terminated with '\'.
; If path is left blank or .\ is used the current working
; directory will be used for DocDBPath.
;=========================================================================
[ViewDoc]
StartPath=.\
[end_ViewDoc]

;=========================================================================
; [Tis]
; SelfTest
; If "On", TIS will automatically make it's own selections
; covering all browse paths of the current CD.
; Otherwise, set to "Off".
; EventDelay
; Specifies the amount of time in milliseconds to wait between calls
; to show a document. This is the recovery period needed by DocDB/DDE.
;
;=========================================================================
[Tis]
SelfTest=Off
EventDelay=4000
[end_Tis]

;=========================================================================
; [Diagnostics]
;
; DocDBStatus
; Whether to use DOCDB or not (On or Off)
;
;=========================================================================
[Diagnostics]
DocDBStatus=On
TacticINIPath=C:\RDS
[end_Diagnostics]

;=========================================================================
; [DealerInfo]
;
; Name
; The name of the dealership.
; Street
; The street address of the dealership.
; Town
; The town name of the dealership.
; Village
; The village name of the dealership.
; County
; The county and postcode of the dealership.
; Phone
; The telephone number of the dealership.
;
;=========================================================================
[DealerInfo]
Name=""
Street=
Town=""
Village=
County=
Phone=
[end_DealerInfo]

;=========================================================================
; [BJC-Limits]
; BJC limitations retrieving data from ADB in hosted mode
;
; BookingsInList
; This defines the max. number of bookings downloaded for the
; Booking Selection list. Keeping this at a resonable number
; will prevent overloading the system by transfering less data.
; (if this key is not set, the default will be 10)
;
; JobsPerBooking
; This defines the max. number of jobs per booking downloaded from the
; host.
; (if this key is not set, the default will be 10)
;
; BookingListFilter:
; valid filters (booking status)
; INITIATED 1; ABORTED 2; SCHEDULED 3
; RESCHEDULED 4; HANDED_OVER 5; IN_WORKSHOP 6
; RDS_ACTIVE 7; COMPLETED_IN_PART 8; REBOOKED 9
; COLLECT_REBOOKED 10; COMPLETED_IN_FULL 12; VEHICLE_COLLECTED 13
; CANCELLED 14; REVIEWED 15; SUSPENDED 16
;
; UploadVehicleLogs:
; This applies for hosted mode only. Set to 'yes' if you want the
; vehicle logs created by diagnostics to be uploaded to the host
; system. If missing or set to value other than 'yes' the logs
; will not be uploaded but ERASED instead.
;
;=========================================================================
[BJC-Limits]
BookingsInList=10
JobsPerBooking=8
BookingListFilter=6
UploadVehicleLogs=no
[end_BJC-Limits]


;=========================================================================
; [VINValidation]
;
; Here a mask for valid characters that are expected in a VIN can be specified
;
; The rules are:
; The length of the mask reflects the max length of a VIN.
;
; '?' denotes that at this position an alpha character is expected
; '#' denotes that at this position a digit character is expected
; '*' denotes that at this position any character is expected (don't care)
;
; Other characters may be used at any position to specify that exactly
; this character is expected at the given position.
;
; Example:
;
; VINmask=SAX???#####****** means that the VIN can have max. 17 positions
; The first 3 positions must be capital SAX. The following 3 positions
; must be alpha chars. The next 5 positions must be digits. The
; remaining 6 positions can be any character (don't care).
;
;=========================================================================
[VINValidation]
VINmask=???*********#####
[end_VINValidation]

;=========================================================================
; [NETIPC]
; NetIPC configurable parameters
;
; TickConnect:
; Number of milliseconds to set connection timer. This is the
; delay period that will be used between connection attempts to
; the MASTER host system. A minimum of 1000 is enforced.
;
; NETSendRecvWait:
; Number of seconds to wait for netcom a send or recv operation to
; succede. A minimum of 1 second is enforced.
;
; FTOHandshakeWait:
; Number of seconds to wait for FTO to establish communication
; with host FTO. A minimum of 1 seconds is enforced.
;
; FTOSendRecvWait:
; Number of seconds to wait for FTO a send or recv operation to
; succede. A minimum of 1 second is enforced.
;
; HPnetDir:
; Directory where networking is installed. The file protocol.ini
; must be located in this directory. This file and the hosts file
; are modified when a new RDS system is initialized.
;
;=========================================================================
[NETIPC]
TickConnect=2000
FTOHandshakeWait=30
FTOSendRecvWait=5
NETSendRecvWait=5
HPnetDir=c:/hpnet
[end_NETIPC]

;=========================================================================
; [CBT]
; CBT Tutorial section. This defines the runstring of the application
; which is to run when the CBT button is selected.
;
; CBTTutorial= value not used anymore ...
;
; KGP: Now separated into 2 parts the Exe and the Dir in which tutorial
; runs.
;
;=========================================================================
[CBT]
; CBTTutorial=Z:\bin\testbook.exe Z:\bin\
CBTTutorialExe=Z:\bin\testbook.exe
CBTTutorialDir=Z:\bin\
CBTTutorial=Z:\bin\testbook.exe Z:\bin\
[end_CBT]

;=========================================================================
; [Touch]
;
; defines where the touch screen 'align' executable is
; The first line following this is for TB1, the second for TB2 & TBA.
;align=c:\mts\touch95\winpanel.exe
;align=c:\windows\control monmouse.cpl
;=========================================================================
[Touch]
[end_Touch]

;=========================================================================
; [VersionControl]
;
; The following defines what files DISCUS will include in the
; RIT Version Control listbox. Two types of inclusions are possible :-
;
; Dirs
; Specifies path name(s) and may include wild cards. All files
; matching the specification in the specified directory are
; included. The key comprises a string in quotes with each
; path separated from the next by a comma.
; Files
; Species path name(s) that may not contain wild cards ie a
; specific file. The key comprises a string in quotes with each
; path separated from the next by a comma.
;
; The final key in this section determines whether version control is
; presented on the RIT menu or not. ON=presented, not otherwise
;
; A maximum of 24 paths may be specified. If the total exceeds this then
; excess entries are ignored.
;
; DISCUS Version Control has the following paths built in :-
;
; c:\rds\bin\*.exe ie all DISCUS executables
; c:\rds\dll\*.dll ie all DISCUS DLLs
; c:\rds\*.lng ie all DISCUS language catalogues
; c:\windows\*.ini ie all Windows INI files
; c:\rds\standalo.bat DISCUS boot batch file
; c:\rds\langmap. DISCUS language map
; c:\rds\rds.ini DISCUS INI file - this file !
;
; eg
; Selected=ON
; Dirs="c:\apps\*.exe, c:\apps\*.dll"
; Files="c:\widget1.exe, c:\widget2.exe, c:\widget3.exe"
;
;=========================================================================
[VersionControl]
Selected=OFF
Dirs=
Files=
[end_VersionControl]

;=========================================================================
; [Config]
; These are some options available to the operator via the
; configuration screen.
;
; ScrollBarTouch
; Wide or Slim, to change the effective width of the scrollbar
; touch area when selected.
;
; ButtonBeep
; On or Off, to allow audio feedback to be enabled/disabled.
;
; CommsLayer=<xx> - sets the vnet or vpas dll layer
; CommsIndex=<xx> - gives the index in the welcome config list box
; UpdateVendor2Reg=<1/0> - update the registry for Vendor2 use, i.e.: Omitec
;
;=========================================================================
[Config]
ScrollBarTouch=Slim
ButtonBeep=Off
CommsLayer=VPAS
CommsIndex=1
UpdateVendor2Reg=1
UseComms=VPAS
;UseComms=NSLI
;UseComms=VPAS
[end_Config]

;=========================================================================
; [Language]
;
; This section keeps track of the currently selected DISCUS language.
; This is used by the NLS support routines. Note these values get
; updated whenever the operator changes language!
;
; LangExt
; The currently selected letter designating the language. e.g. 'e'
; LangDir
; The name of the sub-directory in which this language is identified
; on the document CD.
;
;=========================================================================
[Language]
LangExt=e
LangDir=english
LangRef=eng
[end_Language]

;=========================================================================
[Startup]
LastCD=NoCD
[end_Startup]

;=========================================================================
[Network]
ComputerName=
[end_Network]

;=========================================================================
[Update]
MinDiscSpace=3
[end_Update]

;=========================================================================
; [KillTactics]
; With no entries, defaults to Dirs=<drive>:\bin & Kill=yes.
;
; "Dirs" entry should comprise absolute path(s), and can contain multiple
; Directory paths, separated by ";" - e.g. like a PATH statement.
; NOTE that max length of this string is 60 chars.
; "Kill" entry will disable Killing of Tactics @ Welcome screen if set
; to "no".
;
;=========================================================================
[KillTactics]
Dirs=Z:\bin
Kill=yes
[end_KillTactics]

;=========================================================================
[HelpDesk]
RdsEng_Voice=Tel: +44 (0) 1993 886 199
RdsEng_Fax=Tel: +44 (0) 1993 886 101
;
RdsJpn_Voice=Tel: +44 (0) 1993 886 199
RdsJpn_Fax=Tel: +44 (0) 1993 886 101
;
RdsGrk_Voice=Tel: +44 (0) 1993 886 199
RdsGrk_Fax=Tel: +44 (0) 1993 886 101
[end_HelpDesk]


[RdsIniEnd]

;=========================================================================
; END OF RDS.INI
;
; Note that the blank section name [RdsIniEnd] immediately above serves a
; useful purpose - it prevents DISCUS writing entries for the [Language]
; section below this comment! This does not cause technical problems, but
; it can look a little confusing.
;=========================================================================

[LogFile]
MaxLogFileSize=32767
LogFilePath=c:\rds\logfile.txt
[end_LogFile]

[PreloadData]
NumFiles=1200
PreloadSize=8200000
CheckOnRemove=no
SourceDir=C:\RDS\NEWPRELD\
ListBoxCase=L
DefaultChar=¹
DeleteTheDlls=1
[end_PreloadData]

[T4 Mobile +]
OmitecVendorId=
J2534DeviceId=
[end_T4 Mobile +]

; Search for t4bitmap directory in Drive=<x>
[cd_bmps]
;Drive=d:\
Drive=
[end_cd_bmps]


;=========================================================================
; NOTE: c:\rdsbuild\Common\RDSINC\rds.ini
; <=>
; \\omitec-cov1\rds\DISCUS31\RDS\COMMON\RDSINC\RDS.INV
;=========================================================================
<<Edited by moderator to move content to spoiler for ease of reading the thread.>>
 

Similar threads


ASK THE COMMUNITY

TRENDING THREADS