xp inf file - modify for win7 32bit

NTDEV
1

Hi!

I am pretty desperate.
Since weeks we are trying to get this Orex PccR1417 to run on win7 32 bit, but I assume because of lack of know how *fg* it’ll just never happen.

“Never giove up” they say - so I decided to post my issue here, knowing that I am possibly completely off topic. plz forgive.

anyways, can somebody give me a hint, how to make this *.inf file for xp(latest) to do what it’s supposed to do for win7 32 bit:

;; Orex02.inf

;; ********* PLEASE READ ***********
;; The wizard cannot create exact INF files for all buses and device types.
;; You may have to make changes to this file in order to get your device to
;; install. In particular, hardware IDs and logical configurations require
;; intervention.
;;
;; The NT5DDK documentation contains an excellent INF reference.

;--------- Version Section ---------------------------------------------------

[Version]
Signature=“$Windows 95$”
Provider=%ProviderName%

; If device fits one of the standard classes, use the
; name and GUID here, otherwise create your own as
; this example shows.

Class=Image
ClassGUID={6bdd1fc6-810f-11d0-bec7-08002be2092f}

;--------- SourceDiskNames and SourceDiskFiles Section -----------------------

; These sections identify source disks and files for installation. They are
; shown here as an example, but commented out.

;[SourceDisksNames]
;1 = “Install Disk”,Disk1,

;[SourceDisksFiles]
;Orex02.sys = 1,

;--------- ClassInstall/ClassInstall32 Section -------------------------------

; Not necessary if using a standard class

; 9X Style
[ClassInstall]
Addreg=Class_AddReg

; NT Style
[ClassInstall32]
Addreg=Class_AddReg

[Class_AddReg]
HKR,%DeviceClassName%
HKR,Icon,“-18”

;--------- DestinationDirs Section -------------------------------------------

[DestinationDirs]
Orex02_Files_Driver = 10,System32\Drivers

;--------- Manufacturer and Models Sections ----------------------------------

[Manufacturer]
%MfgName%=Mfg0

[Mfg0]
%DeviceDesc%=Orex02_DDI, USB\VID_0A59&PID_A002

;---------- DDInstall Sections -----------------------------------------------
; --------- Windows 9X -----------------

; Experimentation has shown that DDInstall root names greater than 19 characters
; cause problems in Windows 98

[Orex02_DDI]
CopyFiles=Orex02_Files_Driver
AddReg=Orex02_9X_AddReg

[Orex02_9X_AddReg]
HKR,DevLoader,*ntkern
HKR,NTMPDriver,Orex02.sys
HKR, “Parameters”, “BreakOnEntry”, 0x00010001, 0

; --------- Windows NT -----------------

[Orex02_DDI.NT]
CopyFiles=Orex02_Files_Driver
AddReg=Orex02_NT_AddReg

[Orex02_DDI.NT.Services]
Addservice = Orex02, 0x00000002, Orex02_AddService

[Orex02_AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\Orex02.sys

[Orex02_NT_AddReg]
HKLM, “System\CurrentControlSet\Services\Orex02\Parameters”,\
“BreakOnEntry”, 0x00010001, 0

; --------- Files (common) -------------

[Orex02_Files_Driver]
Orex02.sys

;--------- Strings Section ---------------------------------------------------

[Strings]
ProviderName=“Orex”
MfgName=“”
DeviceDesc=“Orex Ver(2000)(M) 4.5.1.05”
SvcDesc=“Orex Ver(2000)(M) 4.5.1.05”

it is recognising the driver but the wizard gives back:
“Not enough storage to complete this command.” and this xray scanner remains in device manager without a driver as unknown device under imagiing devices.
this is a very “basic” device, so we “assume” it working under win7 32bit.

please help.
with many thanks in advance
peter

2

Though I’m not sure if it matters at all, Signature needs to be $Windows NT$

Does the driver load at all? Do you see the load event in the debugger? Does WIndows PNP create service entry, and the devnode?

3

What does setupapi.dev.log say? It should give you more specific errors and results

d

Bent from my phone

From: xxxxx@yahoo.commailto:xxxxx
Sent: ?4/?19/?2014 2:22 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] xp inf file - modify for win7 32bit

Hi!

I am pretty desperate.
Since weeks we are trying to get this Orex PccR1417 to run on win7 32 bit, but I assume because of lack of know how fg it’ll just never happen.

“Never giove up” they say - so I decided to post my issue here, knowing that I am possibly completely off topic. plz forgive.

anyways, can somebody give me a hint, how to make this .inf file for xp(latest) to do what it’s supposed to do for win7 32 bit:

__________________________________________________________________________
;; Orex02.inf

;; PLEASE READ*
;; The wizard cannot create exact INF files for all buses and device types.
;; You may have to make changes to this file in order to get your device to
;; install. In particular, hardware IDs and logical configurations require
;; intervention.
;;
;; The NT5DDK documentation contains an excellent INF reference.

;--------- Version Section ---------------------------------------------------

[Version]
Signature=“$Windows 95$”
Provider=%ProviderName%

; If device fits one of the standard classes, use the
; name and GUID here, otherwise create your own as
; this example shows.

Class=Image
ClassGUID={6bdd1fc6-810f-11d0-bec7-08002be2092f}

;--------- SourceDiskNames and SourceDiskFiles Section -----------------------

; These sections identify source disks and files for installation. They are
; shown here as an example, but commented out.

;[SourceDisksNames]
;1 = “Install Disk”,Disk1,

;[SourceDisksFiles]
;Orex02.sys = 1,

;--------- ClassInstall/ClassInstall32 Section -------------------------------

; Not necessary if using a standard class

; 9X Style
[ClassInstall]
Addreg=Class_AddReg

; NT Style
[ClassInstall32]
Addreg=Class_AddReg

[Class_AddReg]
HKR,%DeviceClassName%
HKR,Icon,“-18”

;--------- DestinationDirs Section -------------------------------------------

[DestinationDirs]
Orex02_Files_Driver = 10,System32\Drivers

;--------- Manufacturer and Models Sections ----------------------------------

[Manufacturer]
%MfgName%=Mfg0

[Mfg0]
%DeviceDesc%=Orex02_DDI, USB\VID_0A59&PID_A002

;---------- DDInstall Sections -----------------------------------------------
; --------- Windows 9X -----------------

; Experimentation has shown that DDInstall root names greater than 19 characters
; cause problems in Windows 98

[Orex02_DDI]
CopyFiles=Orex02_Files_Driver
AddReg=Orex02_9X_AddReg

[Orex02_9X_AddReg]
HKR,DevLoader,*ntkern
HKR,NTMPDriver,Orex02.sys
HKR, “Parameters”, “BreakOnEntry”, 0x00010001, 0

; --------- Windows NT -----------------

[Orex02_DDI.NT]
CopyFiles=Orex02_Files_Driver
AddReg=Orex02_NT_AddReg

[Orex02_DDI.NT.Services]
Addservice = Orex02, 0x00000002, Orex02_AddService

[Orex02_AddService]
DisplayName = %SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %10%\System32\Drivers\Orex02.sys

[Orex02_NT_AddReg]
HKLM, “System\CurrentControlSet\Services\Orex02\Parameters”,<br> “BreakOnEntry”, 0x00010001, 0

; --------- Files (common) -------------

[Orex02_Files_Driver]
Orex02.sys

;--------- Strings Section ---------------------------------------------------

[Strings]
ProviderName=“Orex”
MfgName=“”
DeviceDesc=“Orex Ver(2000)(M) 4.5.1.05”
SvcDesc=“Orex Ver(2000)(M) 4.5.1.05”
__________________________________________________________________________

it is recognising the driver but the wizard gives back:
“Not enough storage to complete this command.” and this xray scanner remains in device manager without a driver as unknown device under imagiing devices.
this is a very “basic” device, so we “assume” it working under win7 32bit.

please help.
with many thanks in advance
peter

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>

4

Hello!

Thanks for helping us out.

I found the file specified. (attached: setupapi.dev.log)

I think at the very end of this log you can see our multiple successless trys to run the inf to install the sys

But sorry, I cannot not tell what those lines mean, at least enough to figure out what is going wrong. So I attached it (mail). Please feel free to check it.

However, what we did additionally: we “reconstructed” couple of reg entries, as we were supposed to “read” them out of the inf. If necessary, i can supply couple of screenshot, so you can check on those. But we hadn’t any success with rebuilding entries and services in the registry, unfortunately.

setupapi.dev.log (relevant passages):please look mail (I think too long)

5

@ Alex Grig: I dont know; but this “reference” at least works best int this inf, isn’t it? please check setupapi.dev.log for details.

thanks for your help in advance!

greets
peter

6

> we “reconstructed” couple of reg entries

Which specific reg keys did you reconstruct outside of the inf?

d

Bent from my phone

From: xxxxx@yahoo.commailto:xxxxx
Sent: ?4/?20/?2014 2:22 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] xp inf file - modify for win7 32bit

Hello!

Thanks for helping us out.

I found the file specified. (attached: setupapi.dev.log)

I think at the very end of this log you can see our multiple successless trys to run the inf to install the sys

But sorry, I cannot not tell what those lines mean, at least enough to figure out what is going wrong. So I attached it (mail). Please feel free to check it.

However, what we did additionally: we “reconstructed” couple of reg entries, as we were supposed to “read” them out of the inf. If necessary, i can supply couple of screenshot, so you can check on those. But we hadn’t any success with rebuilding entries and services in the registry, unfortunately.

setupapi.dev.log (relevant passages):please look mail (I think too long)
__________________________________________________________

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>

7

Hello!

I made some screenshots. should be sufficient.
Is this exactly what the inf would do to the registry if it was running properly?

We installed the driver on a xp engine where it went through smoothly and looked at the reg there. we pretty much copied the entries as good as we could because we figured that running the inf under win7 32 bit isn’t basicaly changing anything to the reg.

did you check on “setupapi.dev.log”?

greets

peter
 

 

From: Doron Holan
To: Windows System Software Devs Interest List
Sent: Sunday, April 20, 2014 5:30 PM
Subject: RE: [ntdev] xp inf file - modify for win7 32bit

> we “reconstructed” couple of reg entries

Which specific reg keys did you reconstruct outside of the inf?

d

Bent from my phone

________________________________
From: xxxxx@yahoo.com
Sent: ‎4/‎20/‎2014 2:22 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] xp inf file - modify for win7 32bit

Hello!

Thanks for helping us out.

I found the file specified. (attached: setupapi.dev.log)

I think at the very end of this log you can see our multiple successless trys to run the inf to install the sys

But sorry, I cannot not tell what those lines mean, at least enough to figure out what is going wrong. So I attached it (mail). Please feel free to check it.

However, what we did additionally: we “reconstructed” couple of reg entries, as we were supposed to “read” them out of the inf. If necessary, i can supply couple of screenshot, so you can check on those. But we hadn’t any success with rebuilding entries and
services in the registry, unfortunately.

setupapi.dev.log (relevant passages):please look mail (I think too long)
__________________________________________________________

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

8

xxxxx@yahoo.com wrote:

I am pretty desperate.
Since weeks we are trying to get this Orex PccR1417 to run on win7 32 bit, but I assume because of lack of know how *fg* it’ll just never happen.

I don’t see any huge issues here. You have a number of things here that
are unnecessary. As the comments say, you should not include the
[ClassInstall] sections for a standard device class, and you are using a
standard device class. The [Orex02_9X_AddReg] section is also
unnecessary; all of that was for Windows 95 and 98.

I noticed that MfgName string is null. I don’t know whether that is
invalid, but it is certainly suspicious.

By the way, your setup.dev.log did not make it through to the mailing
list. You might consider putting that on a web page somewhere and
posting a link.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.