RAMDisk and HardDisk strikes back!

G

Guest

Hi folks,

I have a problem with XPe RAM boot and the hard disk volume mapping.
After running FBA and doing registry modifications described by Slobodon and
Pieter in
http://groups.google.com/[email protected]#link9,
the IDE Disk was detectable and mountable from RAMDisk image only if two HDs
are presents. BTW, when the HD is alone, the RAMDisk image isn't capable to
mount the disk. Only RAMDisk device is visible as C:\. In this case, PnP
driver load fails with error CM_PROB_DRIVER_FAILED_LOAD - "Windows cannot
load the device driver for this hardware. The driver may be corrupted or
missing. (Code 39)" as reported by Setupapi.log.

I have modified the registry with the settings described by Slobodan:

1) Deleted all registry kery from
“HKEY_LOCAL_MACHINE\SYSTEM\MountedDevicesâ€
(also the 'MountedDevices' key)

2) Deleted “SystemPartition†key from
“HKEY_LOCAL_MACHINE\SYSTEM\Setupâ€

In any case, the RAMDisk image not mounts the HD partitions or the new HD to
format. If I plug-in an USB device, like a CF or HD, the drive letter mapping
fail everytime.

How is possible to solve this problems? I try several combinations but the
problem
still here yet! Any suggests are welcome!

Many thanks in advance for any assistance.

Best regards,

Paolo Margari


--------------------------------------------------------------------------------

Dr. Paolo Margari, PHD
Research & Development Director

Studio di Informatica
via L. Sanfelice, 25
I-50133 Firenze - Italy

Tel. +39 055 561420
Fax +39 055 81131184
mobile +39 335 6122211

e-mail: (e-mail address removed)
(e-mail address removed)

----------------------------------
Privacy and Confidentiality Notice:
The information contained in this electronic mail message is intended for
the named recipient(s) only. It may contain privileged and confidential
information. If you are not an intended recipient, you must not copy,
forward, distribute or take any action in reliance on it. If you have
received this electronic mail message in error, please notify the sender
immediately.
----------------------------------
 
S

Slobodan Brcin \(eMVP\)

Hi Paolo,

It looks that you have problem with disk.sys driver that is much on lover level in drivers chain that volume letter assignment.
Since if you don't have disk driver then partitions and volumes are never exposed.

Quick try would be to use HDD that is different from HDD that you used during the FBA. Also you can try with HDD that you used
during the FBA, just to compare results.
Before creating SDI file, please delete setupapi.log. (Optionally in registry increase log detailed shown by setupapi)

When you boot from SDI file your setupapi.log will contain only information's related to why your disk failed to start. Please send
this file in this NG.

This also could be PnP related problem (Please check that you have User Mode PnP component)

Regards,
Slobodan
 
K

KM

Slobodan,
This also could be PnP related problem (Please check that you have User Mode PnP component)
Click to expand...

Isn't that has to be "PnP (Kernel-Mode)" component only for the disk.sys related problems?
It does not hurt to have User Mode PnP component too. But it may be required mostly for accessing PnP stuff from user mode apps
(like FBA or etc).

KM
 
S

Slobodan Brcin \(eMVP\)

Konstantin,

Actually I'm not sure about User Mode PnP (But he should try with it since it can't hurt, but not having it can).

He should also remove from offline registry:HKLM\System\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk
To prevent disk driver usage before it is installed from inf file. This will avoid driver start then stop for better installation.

Regards,
Slobodan
 
G

Guest

Hi Slobodan,

I have tried more times to boot the system in different scenario:

1) Only one disk without any partition;
2) One disk with only one partition as large as FBA setup;
3) One disk with two partitions different in size;
4) Two disk with one or more partitions for each.

The results are:

1) The system works fine and I may run the DISKPART to init the disk;
2) The system works fine without problems;
3) The User PnP reports an error while enumerating new hardware, and the
partitions aren't visible;
4) The system works fine without problems.

I have repeated the tests in another system with the same hardware setup but
different HD type and partitions.
The results are strange:

1), 2), 3) The User PnP reports an error while enumerating new hardware, and
the partitions aren't visible;
4) The system works fine without problems.

The Setupapi.log reports only the same error like this:

[..........]
@ 20:32:55.242 #T075 Enumerating files: Directory pass completed.
@ 20:32:55.252 #T076 Enumerating files: Cache pass completed.
@ 20:32:55.252 #V166 Device install function: DIF_SELECTBESTCOMPATDRV.
@ 20:32:55.252 #V155 Executing default installer.
@ 20:32:55.252 #W059 Selecting best compatible driver failed. Error
0xe0000228: There are no compatible drivers for this device.
@ 20:32:55.252 #W157 Default installer failed. Error 0xe0000228: There are
no compatible drivers for this device.
[....................]

or like this if the disk has two partitions (this trace is present more
times in the log file):

[...........................]
@ 20:53:51.166 #T200 Install Device: Begin.
@ 20:53:51.166 #I123 Doing full install of
"IDE\DISKIBM-DJNA-372200_________________________J71OA30K\4&2C5D936F&0&0.0.0".
@ 20:53:51.166 #V042 Opened INF "c:\windows\inf\disk.inf", PNF created
(Languge = 0409).
@ 20:53:51.166 #T211 Install Device: Changing registry settings as specified
by the INF(s).
@ 20:53:51.176 #T212 Install Device: Writing driver specific registry
settings.
@ 20:53:51.176 #T213 Install Device: Installing required Windows services.
#-035 Processing service Add/Delete section [disk_install.NT.Services].
@ 20:53:51.176 #V282 Add Service: Modified existing service "disk".
@ 20:53:51.176 #V268 Controlling Service: Service "disk" is required at
boot, modifying filter drivers.
@ 20:53:51.176 #T214 Install Device: Writing driver descriptive registry
settings.
@ 20:53:51.186 #T218 Install Device: Removing device sub-tree.
@ 20:53:52.338 #T219 Install Device: Removing device sub-tree completed.
@ 20:53:52.338 #T216 Install Device: Restarting device.
@ 20:53:52.348 #T217 Install Device: Restarting device completed.
@ 20:53:52.358 #I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
@ 20:53:52.358 #T222 Install Device: Calling 'RUNONCE'/'GRPCONV' items.
@ 20:53:52.358 #I121 Device install of
"IDE\DISKIBM-DJNA-372200_________________________J71OA30K\4&2C5D936F&0&0.0.0"
finished successfully.
@ 20:53:52.358 #T201 Install Device: End.
[.................]

What is happened? I need a small XPe system to restore the HDs in my
embedded systems, but the configurations of them are not the same for all!

How I may solve this problem? Thanks a lot,

Paolo


-------------------------------------------------------------------------------------
 
P

Pieter

Hi Paolo,

I observed the same problems. Except for issue 4. I did not not test such a
configuration.
My solution was to clean Contolset001\control\class. It only contains the
following
classes: RAMDISK, COMPUTER, KEYBOARD, MOUSE, NET, NETCLIENT, NETSERVICE and
NETTRANS.

Regards,
Pieter


Paolo Margari said:
Hi Slobodan,

I have tried more times to boot the system in different scenario:

1) Only one disk without any partition;
2) One disk with only one partition as large as FBA setup;
3) One disk with two partitions different in size;
4) Two disk with one or more partitions for each.

The results are:

1) The system works fine and I may run the DISKPART to init the disk;
2) The system works fine without problems;
3) The User PnP reports an error while enumerating new hardware, and the
partitions aren't visible;
4) The system works fine without problems.

I have repeated the tests in another system with the same hardware setup
but
different HD type and partitions.
The results are strange:

1), 2), 3) The User PnP reports an error while enumerating new hardware,
and
the partitions aren't visible;
4) The system works fine without problems.

The Setupapi.log reports only the same error like this:

[..........]
@ 20:32:55.242 #T075 Enumerating files: Directory pass completed.
@ 20:32:55.252 #T076 Enumerating files: Cache pass completed.
@ 20:32:55.252 #V166 Device install function: DIF_SELECTBESTCOMPATDRV.
@ 20:32:55.252 #V155 Executing default installer.
@ 20:32:55.252 #W059 Selecting best compatible driver failed. Error
0xe0000228: There are no compatible drivers for this device.
@ 20:32:55.252 #W157 Default installer failed. Error 0xe0000228: There are
no compatible drivers for this device.
[....................]

or like this if the disk has two partitions (this trace is present more
times in the log file):

[...........................]
@ 20:53:51.166 #T200 Install Device: Begin.
@ 20:53:51.166 #I123 Doing full install of
"IDE\DISKIBM-DJNA-372200_________________________J71OA30K\4&2C5D936F&0&0.0.0".
@ 20:53:51.166 #V042 Opened INF "c:\windows\inf\disk.inf", PNF created
(Languge = 0409).
@ 20:53:51.166 #T211 Install Device: Changing registry settings as
specified
by the INF(s).
@ 20:53:51.176 #T212 Install Device: Writing driver specific registry
settings.
@ 20:53:51.176 #T213 Install Device: Installing required Windows services.
#-035 Processing service Add/Delete section [disk_install.NT.Services].
@ 20:53:51.176 #V282 Add Service: Modified existing service "disk".
@ 20:53:51.176 #V268 Controlling Service: Service "disk" is required at
boot, modifying filter drivers.
@ 20:53:51.176 #T214 Install Device: Writing driver descriptive registry
settings.
@ 20:53:51.186 #T218 Install Device: Removing device sub-tree.
@ 20:53:52.338 #T219 Install Device: Removing device sub-tree completed.
@ 20:53:52.338 #T216 Install Device: Restarting device.
@ 20:53:52.348 #T217 Install Device: Restarting device completed.
@ 20:53:52.358 #I163 Device not started: Device has problem: 0x27:
CM_PROB_DRIVER_FAILED_LOAD.
@ 20:53:52.358 #T222 Install Device: Calling 'RUNONCE'/'GRPCONV' items.
@ 20:53:52.358 #I121 Device install of
"IDE\DISKIBM-DJNA-372200_________________________J71OA30K\4&2C5D936F&0&0.0.0"
finished successfully.
@ 20:53:52.358 #T201 Install Device: End.
[.................]

What is happened? I need a small XPe system to restore the HDs in my
embedded systems, but the configurations of them are not the same for all!

How I may solve this problem? Thanks a lot,

Paolo


-------------------------------------------------------------------------------------
Slobodan Brcin (eMVP) said:
Hi Paolo,

It looks that you have problem with disk.sys driver that is much on lover
level in drivers chain that volume letter assignment.
Since if you don't have disk driver then partitions and volumes are never
exposed.

Quick try would be to use HDD that is different from HDD that you used
during the FBA. Also you can try with HDD that you used
during the FBA, just to compare results.
Before creating SDI file, please delete setupapi.log. (Optionally in
registry increase log detailed shown by setupapi)

When you boot from SDI file your setupapi.log will contain only
information's related to why your disk failed to start. Please send
this file in this NG.

This also could be PnP related problem (Please check that you have User
Mode PnP component)

Regards,
Slobodan
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

SDI boot from RAM 5

Top