USB Printer Problem

  • Thread starter Thread starter BTN
  • Start date Start date
B

BTN

Hi!

I am trying to make a printer component from an INF file, but during import
I get: <<Cannot handle key: "DataSection">>

The data-section looks like this:

[RASDD_DATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR%

Any way of manually entering this information in Component Designer?

I tried building an image anyway, but the printer does not work..

Thanx,
BN
 
Hi Slobodan,

Thank You for the response..:)

I can install the printer manually, using "Add Printer". I have read lots of
posts today, and tried everything suggested. I will do a registry and file
scan before and after adding the printer manually now.. Hopefully there is a
file or registry entry I have forgotten...

Thanx,
BN

Slobodan Brcin (eMVP) said:
Hi BN,

Basically this section alone means nothing. So you we can't tell where you
should put these data.
Have you done simple test can you install manually printer driver on XPe
and make it work?

Read trough this search:
http://groups-beta.google.com/group...ublic.windowsxp.embedded&q=USB+printer&qt_g=1

Regards,
Slobodan


BTN said:
Hi!

I am trying to make a printer component from an INF file, but during
import
I get: <<Cannot handle key: "DataSection">>

The data-section looks like this:

[RASDD_DATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR%

Any way of manually entering this information in Component Designer?

I tried building an image anyway, but the printer does not work..

Thanx,
BN
Click to expand...
Click to expand...
 
Hi....

It seems that FBA returns the following error code:

[PnpEnumThread: AllowInstall] SetupDiCallClassInstaller Error: 0x5b3,
Device: USB Printer

ERROR_REQUIRES_INTERACTIVE_WINDOWSTATION

Anywone seen this before?

Thanx,
BN
 
BTN,

Do you want to show us the entire INF file?

Also, you may want to create just a simple component that will copy the printer driver files to appropriate windows directories.
Then PnP will install the printer.
 
Hi KM,

There is no "Found New Hardware" wizard popping up, I can only make it work
when I manualy install it using "Add Printer".

Here is the INF file:

; CUSTOM
; oemsetup.INF
;
; Printer INF for NT 4.0 and Win 2000.
; List of supported printers, manufacturers
;

[Version]
Signature="$Windows NT$"
Provider=%CE%
LayoutFile=layout.inf
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer

;
; Call SetupSetDirectoryId with 66000 to set the target directory at runtime
; (depending on which environment drivers are getting installed)
;
[DestinationDirs]
DefaultDestDir=66000
DRVDESTFILE=66000
SYS32=11


[SourceDisksNames.x86]
1 = %Disk1%,,,""

[SourceDisksFiles]
oemsetup.inf =1
vkp802.dll =1
celm.dll =1
cepmlm.exe =1
cesmlm.dll =1
rasdd.dll =1,i386
rasddui.dll =1,i386
rasddui.hlp =1,i386

;
; Manufacturer section.
;
; This section lists all of the manufacturers
; that we will display in the Dialog box
;
[Manufacturer]
"CUSTOM"

;
; Model sections.
;
; Each section here corresponds with an entry listed in the
; [Manufacturer] section, above. The models will be displayed in the order
; that they appear in the INF file.
;

[CUSTOM]
"Custom VKP80 (200dpi)"=Vkp802.dll, custom_engineeringvkac55
;
; Installer Sections
;
; These sections control file installation, and reference all files that
; need to be copied. The section name will be assumed to be the driver
; file, unless there is an explicit DriverFile section listed.
;

[Vkp802.dll]
[email protected],RASDD,SYS32,DRVDESTFILE
DataSection=RASDDDATA

; Copy Sections
;
; Lists of files that are actually copied. These sections are referenced
; from the installer sections, above. Only create a section if it contains
; two or more files (if we only copy a single file, identify it in the
; installer section, using the @filename notation) or if it's a color
; profile (since the DestinationDirs can only handle sections, and not
; individual files).
;

[RASDD]
RASDD.DLL
RASDDUI.DLL
RASDDUI.HLP

; System files
[SYS32]
cepmlm.exe
cesmlm.dll


[DRVDESTFILE]
cepmlm.exe
cesmlm.dll

;
; Data Sections
;
; These sections contain data that is shared between devices.
;

[RASDDDATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR% ; Language monitor


;
; Localizable Strings
;
[Strings]
CE="Custom Engineering"
Disk1="VKP80 Drivers Disk"
CEL_MONITOR="celm.dll: kpm language monitor,celm.dll"



KM said:
BTN,

Do you want to show us the entire INF file?

Also, you may want to create just a simple component that will copy the
printer driver files to appropriate windows directories.
Then PnP will install the printer.

--
Regards,
KM, BSquare Corp.

Hi!

I am trying to make a printer component from an INF file, but during
import
I get: <<Cannot handle key: "DataSection">>

The data-section looks like this:

[RASDD_DATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR%

Any way of manually entering this information in Component Designer?

I tried building an image anyway, but the printer does not work..

Thanx,
BN
Click to expand...
Click to expand...
 
BTN,

Interesting.. the ntprint.inf also has DataSection section that are not understandable by the XPE INF importer.
When you try to import the ntprint.inf you can see the same error message as from your custom INF file import.
I guess this is a bug in CD (INF importer, SP1).

You can do a custom import, though.

The DataSection format is described here:
http://msdn.microsoft.com/library/d..._5a6b18f4-dcee-4e41-9615-8b8ce69f5b4e.xml.asp


You don't need "Found New Hardware" wizard. Just place all the printer driver files to appropriate windows directory and reboot.
Or are you saying there is no PnP event happening for the printer? Anyway, you can always install the printer and capture all its
registry data entries and preinstall them in TD.

--
Regards,
KM, BSquare Corp.

Hi KM,

There is no "Found New Hardware" wizard popping up, I can only make it work
when I manualy install it using "Add Printer".

Here is the INF file:

; CUSTOM
; oemsetup.INF
;
; Printer INF for NT 4.0 and Win 2000.
; List of supported printers, manufacturers
;

[Version]
Signature="$Windows NT$"
Provider=%CE%
LayoutFile=layout.inf
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer

;
; Call SetupSetDirectoryId with 66000 to set the target directory at runtime
; (depending on which environment drivers are getting installed)
;
[DestinationDirs]
DefaultDestDir=66000
DRVDESTFILE=66000
SYS32=11


[SourceDisksNames.x86]
1 = %Disk1%,,,""

[SourceDisksFiles]
oemsetup.inf =1
vkp802.dll =1
celm.dll =1
cepmlm.exe =1
cesmlm.dll =1
rasdd.dll =1,i386
rasddui.dll =1,i386
rasddui.hlp =1,i386

;
; Manufacturer section.
;
; This section lists all of the manufacturers
; that we will display in the Dialog box
;
[Manufacturer]
"CUSTOM"

;
; Model sections.
;
; Each section here corresponds with an entry listed in the
; [Manufacturer] section, above. The models will be displayed in the order
; that they appear in the INF file.
;

[CUSTOM]
"Custom VKP80 (200dpi)"=Vkp802.dll, custom_engineeringvkac55
;
; Installer Sections
;
; These sections control file installation, and reference all files that
; need to be copied. The section name will be assumed to be the driver
; file, unless there is an explicit DriverFile section listed.
;

[Vkp802.dll]
[email protected],RASDD,SYS32,DRVDESTFILE
DataSection=RASDDDATA

; Copy Sections
;
; Lists of files that are actually copied. These sections are referenced
; from the installer sections, above. Only create a section if it contains
; two or more files (if we only copy a single file, identify it in the
; installer section, using the @filename notation) or if it's a color
; profile (since the DestinationDirs can only handle sections, and not
; individual files).
;

[RASDD]
RASDD.DLL
RASDDUI.DLL
RASDDUI.HLP

; System files
[SYS32]
cepmlm.exe
cesmlm.dll


[DRVDESTFILE]
cepmlm.exe
cesmlm.dll

;
; Data Sections
;
; These sections contain data that is shared between devices.
;

[RASDDDATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR% ; Language monitor


;
; Localizable Strings
;
[Strings]
CE="Custom Engineering"
Disk1="VKP80 Drivers Disk"
CEL_MONITOR="celm.dll: kpm language monitor,celm.dll"



KM said:
BTN,

Do you want to show us the entire INF file?

Also, you may want to create just a simple component that will copy the
printer driver files to appropriate windows directories.
Then PnP will install the printer.

--
Regards,
KM, BSquare Corp.

Hi!

I am trying to make a printer component from an INF file, but during
import
I get: <<Cannot handle key: "DataSection">>

The data-section looks like this:

[RASDD_DATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR%

Any way of manually entering this information in Component Designer?

I tried building an image anyway, but the printer does not work..

Thanx,
BN
Click to expand...
Click to expand...
Click to expand...
 
Thanx KM,

I think I will do a preinstall in TD.. Any pointers on what registry data I
should be aware of?

I tried using InCtrl5, but there was really a lot of things changed..

BN

KM said:
BTN,

Interesting.. the ntprint.inf also has DataSection section that are not
understandable by the XPE INF importer.
When you try to import the ntprint.inf you can see the same error message
as from your custom INF file import.
I guess this is a bug in CD (INF importer, SP1).

You can do a custom import, though.

The DataSection format is described here:
http://msdn.microsoft.com/library/d..._5a6b18f4-dcee-4e41-9615-8b8ce69f5b4e.xml.asp


You don't need "Found New Hardware" wizard. Just place all the printer
driver files to appropriate windows directory and reboot.
Or are you saying there is no PnP event happening for the printer? Anyway,
you can always install the printer and capture all its
registry data entries and preinstall them in TD.

--
Regards,
KM, BSquare Corp.

Hi KM,

There is no "Found New Hardware" wizard popping up, I can only make it
work
when I manualy install it using "Add Printer".

Here is the INF file:

; CUSTOM
; oemsetup.INF
;
; Printer INF for NT 4.0 and Win 2000.
; List of supported printers, manufacturers
;

[Version]
Signature="$Windows NT$"
Provider=%CE%
LayoutFile=layout.inf
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer

;
; Call SetupSetDirectoryId with 66000 to set the target directory at
runtime
; (depending on which environment drivers are getting installed)
;
[DestinationDirs]
DefaultDestDir=66000
DRVDESTFILE=66000
SYS32=11


[SourceDisksNames.x86]
1 = %Disk1%,,,""

[SourceDisksFiles]
oemsetup.inf =1
vkp802.dll =1
celm.dll =1
cepmlm.exe =1
cesmlm.dll =1
rasdd.dll =1,i386
rasddui.dll =1,i386
rasddui.hlp =1,i386

;
; Manufacturer section.
;
; This section lists all of the manufacturers
; that we will display in the Dialog box
;
[Manufacturer]
"CUSTOM"

;
; Model sections.
;
; Each section here corresponds with an entry listed in the
; [Manufacturer] section, above. The models will be displayed in the
order
; that they appear in the INF file.
;

[CUSTOM]
"Custom VKP80 (200dpi)"=Vkp802.dll, custom_engineeringvkac55
;
; Installer Sections
;
; These sections control file installation, and reference all files that
; need to be copied. The section name will be assumed to be the driver
; file, unless there is an explicit DriverFile section listed.
;

[Vkp802.dll]
[email protected],RASDD,SYS32,DRVDESTFILE
DataSection=RASDDDATA

; Copy Sections
;
; Lists of files that are actually copied. These sections are referenced
; from the installer sections, above. Only create a section if it
contains
; two or more files (if we only copy a single file, identify it in the
; installer section, using the @filename notation) or if it's a color
; profile (since the DestinationDirs can only handle sections, and not
; individual files).
;

[RASDD]
RASDD.DLL
RASDDUI.DLL
RASDDUI.HLP

; System files
[SYS32]
cepmlm.exe
cesmlm.dll


[DRVDESTFILE]
cepmlm.exe
cesmlm.dll

;
; Data Sections
;
; These sections contain data that is shared between devices.
;

[RASDDDATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR% ; Language monitor


;
; Localizable Strings
;
[Strings]
CE="Custom Engineering"
Disk1="VKP80 Drivers Disk"
CEL_MONITOR="celm.dll: kpm language monitor,celm.dll"



KM said:
BTN,

Do you want to show us the entire INF file?

Also, you may want to create just a simple component that will copy the
printer driver files to appropriate windows directories.
Then PnP will install the printer.

--
Regards,
KM, BSquare Corp.


Hi!

I am trying to make a printer component from an INF file, but during
import
I get: <<Cannot handle key: "DataSection">>

The data-section looks like this:

[RASDD_DATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR%

Any way of manually entering this information in Component Designer?

I tried building an image anyway, but the printer does not work..

Thanx,
BN
Click to expand...
Click to expand...
Click to expand...
 
BTN,

You may want to use tools like RegSnap. Will give you .reg file instead of just text log.

Registry entries.. Service data, Enum data.

Or you can do a command line solution. Something like:
rundll32 printui.dll,PrintUIEntry /if /b "Your printer ID" /f %SystemRoot%\inf\oemsetup.inf /r "lpt1:" /m "Your printer model
name"

Btw, I don't think you necessarily need the DataSection to be parsed. Just make sure that in the imported component you got all the
required files listed.

--
Regards,
KM, BSquare Corp.

Thanx KM,

I think I will do a preinstall in TD.. Any pointers on what registry data I
should be aware of?

I tried using InCtrl5, but there was really a lot of things changed..

BN

KM said:
BTN,

Interesting.. the ntprint.inf also has DataSection section that are not
understandable by the XPE INF importer.
When you try to import the ntprint.inf you can see the same error message
as from your custom INF file import.
I guess this is a bug in CD (INF importer, SP1).

You can do a custom import, though.

The DataSection format is described here:
http://msdn.microsoft.com/library/d..._5a6b18f4-dcee-4e41-9615-8b8ce69f5b4e.xml.asp


You don't need "Found New Hardware" wizard. Just place all the printer
driver files to appropriate windows directory and reboot.
Or are you saying there is no PnP event happening for the printer? Anyway,
you can always install the printer and capture all its
registry data entries and preinstall them in TD.

--
Regards,
KM, BSquare Corp.

Hi KM,

There is no "Found New Hardware" wizard popping up, I can only make it
work
when I manualy install it using "Add Printer".

Here is the INF file:

; CUSTOM
; oemsetup.INF
;
; Printer INF for NT 4.0 and Win 2000.
; List of supported printers, manufacturers
;

[Version]
Signature="$Windows NT$"
Provider=%CE%
LayoutFile=layout.inf
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer

;
; Call SetupSetDirectoryId with 66000 to set the target directory at
runtime
; (depending on which environment drivers are getting installed)
;
[DestinationDirs]
DefaultDestDir=66000
DRVDESTFILE=66000
SYS32=11


[SourceDisksNames.x86]
1 = %Disk1%,,,""

[SourceDisksFiles]
oemsetup.inf =1
vkp802.dll =1
celm.dll =1
cepmlm.exe =1
cesmlm.dll =1
rasdd.dll =1,i386
rasddui.dll =1,i386
rasddui.hlp =1,i386

;
; Manufacturer section.
;
; This section lists all of the manufacturers
; that we will display in the Dialog box
;
[Manufacturer]
"CUSTOM"

;
; Model sections.
;
; Each section here corresponds with an entry listed in the
; [Manufacturer] section, above. The models will be displayed in the
order
; that they appear in the INF file.
;

[CUSTOM]
"Custom VKP80 (200dpi)"=Vkp802.dll, custom_engineeringvkac55
;
; Installer Sections
;
; These sections control file installation, and reference all files that
; need to be copied. The section name will be assumed to be the driver
; file, unless there is an explicit DriverFile section listed.
;

[Vkp802.dll]
[email protected],RASDD,SYS32,DRVDESTFILE
DataSection=RASDDDATA

; Copy Sections
;
; Lists of files that are actually copied. These sections are referenced
; from the installer sections, above. Only create a section if it
contains
; two or more files (if we only copy a single file, identify it in the
; installer section, using the @filename notation) or if it's a color
; profile (since the DestinationDirs can only handle sections, and not
; individual files).
;

[RASDD]
RASDD.DLL
RASDDUI.DLL
RASDDUI.HLP

; System files
[SYS32]
cepmlm.exe
cesmlm.dll


[DRVDESTFILE]
cepmlm.exe
cesmlm.dll

;
; Data Sections
;
; These sections contain data that is shared between devices.
;

[RASDDDATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR% ; Language monitor


;
; Localizable Strings
;
[Strings]
CE="Custom Engineering"
Disk1="VKP80 Drivers Disk"
CEL_MONITOR="celm.dll: kpm language monitor,celm.dll"



"KM" <konstmor@nospam_yahoo.com> skrev i melding
BTN,

Do you want to show us the entire INF file?

Also, you may want to create just a simple component that will copy the
printer driver files to appropriate windows directories.
Then PnP will install the printer.

--
Regards,
KM, BSquare Corp.


Hi!

I am trying to make a printer component from an INF file, but during
import
I get: <<Cannot handle key: "DataSection">>

The data-section looks like this:

[RASDD_DATA]
DriverFile=RASDD.DLL
ConfigFile=RASDDUI.DLL
HelpFile=RASDDUI.HLP
LanguageMonitor=%CEL_MONITOR%

Any way of manually entering this information in Component Designer?

I tried building an image anyway, but the printer does not work..

Thanx,
BN
Click to expand...
Click to expand...
Click to expand...
 
Back
Top