Re: Booting XP(E) via a USB to PCI slotcard

Hi all,

you can begin to count hours, when booting XP(E) via a USB to PCI
slotcard will work.

When formulating as good as possible my own last question about faking
IoAssignArcName() here to the forum, I suddenly found its solution. It
is sooo easy.

Here is the C-source code for my driver arcname.sys, just written in 5
minutes...
(hihi... computers are no humans, you can make them think what ever you
want )



#include <ntddk.h>

WCHAR DeviceNameBuffer[80];
UNICODE_STRING DeviceName;

WCHAR ArcNameBuffer[80];
UNICODE_STRING ArcName;


VOID
{

swprintf(ArcNameBuffer,
L"\\ArcName\\multi(0)disk(0)rdisk(0)partition(1)");


RtlInitUnicodeString (&ArcName,
ArcNameBuffer);



swprintf(DeviceNameBuffer,
L"\\Device\\Harddisk0\\Partition1");


RtlInitUnicodeString(&DeviceName,
DeviceNameBuffer);

IoAssignArcName (&ArcName,
&DeviceName);

}

Do you think this will work?

This can easiest be compiled for NT4, Win2000, Win SP1, SP2 and Windows
2003, and Vista and Embedded SP1, SP2 and Reactos.

And one problem more is gone: I thought, that it may be a problem, to
make this driver start, just before disk.sys starts, not that the silly
XP(E) noticed, that it was faked and tries to zero some values:

I found in the WinDDK the source code for disk.sys.
I only need to put the few lines of my driver direct before the source
code of disk.c and compile them together.
And there is no chance left, that after that XP(E) has a (faked
Yippiehh) arcpath for the USB harddisk,
connected via my USB to PCI slotcard. Whether the new driver disk.sys
works, can be testet at once:
Even if XP(E) starts as normal from a IDE harddisk, if there is a USB
to PCI slotcard with a USB harddisk connected, there is no Arcpath for
that USB harddisk. Klicking on Winobj.exe, shows you at once
and brutal, whether the new driver disk.sys gives this USB harddisk a
Arcpath or not.

The only thing left, that I have to solve then, is the egg-chicken
problem: One day ago I thought, that with the recovery console you cant
start any program: But then I tested the command batch .
So you can run any program via the Recovery Console, simply hided in a
batch file.

Nice to hear from you
Dietmar

PS: Now I know: The blue screen with BSOD 0x7b is in most cases,
because my arcname.sys driver isnt build in, in disk.sys. And that does
Microsoft not know???

.

Relevant Pages