When I begin to select and load my own stor miniport driver during installing Longhorn onto my raid, the BSOD will occur. Since BSOD can occur, I think till that time the debugging mechanism is already installed. So how can I use windbg to connect the target machine at that time, i.e., the early time when Longhorn has just been installed a little and I have even just input my SN and just selected my driver of raid.
You need to look at the installation kit documentation to see how to turn
the debugger on for the text mode setup phase, It is do-able, but offhand I
do not recall how this is done for longhorn. Of course you have already
debugged your driver for longhorn post-install as a non boot device, right?
On Jan 10, 2008 5:21 AM, wrote:
> When I begin to select and load my own stor miniport driver during
> installing Longhorn onto my raid, the BSOD will occur. Since BSOD can
> occur, I think till that time the debugging mechanism is already installed.
> So how can I use windbg to connect the target machine at that time, i.e.,
> the early time when Longhorn has just been installed a little and I have
> even just input my SN and just selected my driver of raid.
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
–
Mark Roddy
Yes, I just don’t know how to debug my stor miniport driver during Longhorn’s installation. Usually after windows is installed, debugging is a common thing.
In windbg’s help, there is an article “Advanced Debugging Techniques\Debugging Windows Setup and the OS Loader”. I am not very sure whether this article is helpful. It seems related with “starting windows”. Now I paste it here:
Debugging Windows Setup and the OS Loader
If your computer hangs in text-mode at the Starting Windows screen and has not connected into the debugger, it may be possible to modify your setup to allow the debugger to connect during startup.
Before debugging can begin, you must start your target computer in Safe Mode and make the following preparations:
Install the checked version of $LDR$ on the target computer. If you install the full checked build of Windows, this file will be included. If you want to install only this file, you need to look for it under the name setupldr.bin. Copy this file to the root of the first bootable partition on the target computer and rename it $LDR$ (with no file name extension). For instructions on how to install a full checked build or individual checked files, see the Windows Driver Kit.
Make sure the symbols for the checked version of $LDR$ are included in the debugger’s symbol path.
Set the debugger baud rate to 19200.
Modify the file txtsetup.sif on the target computer by adding the /debugstop, /debugport, and /baudrate switches to the OsLoadOptions line. Here is an example of a modified txtsetup.sif file:
OsLoadOptions = “/fastdetect /noguiboot /debugstop /debugport=com2 /baudrate=19200”
; OsLoadOptionsVar = “/fastdetect”
; SetupCmdLinePrepend = “CDB”
The exact contents of your file may differ from this. The baud rate should match that used by the debugger (19200 is recommended). The COM port should be the port on the target computer to which the debugging cable is attached.
After these steps have been completed, use the following procedure to connect the debugger:
Debugging Windows Setup and the OS Loader
Start up the debugger with the -d command-line option, or use CTRL+K to cause the debugger to break in when the first kernel module is loaded.
When the debugger breaks in, you will see a message that the symbol checksum cannot be verified. Ignore this message! If you want to verify that your symbols are correct, do a stack trace and make sure the first line of the stack trace says osloader!DbgBreakPoint.
I am sure there is a way to debug “storage” problem while installing Windows. If there is no, then how do all the storage manufactures turn out there products?
Oh, it seems that “txtsetup.sif” is really about “installation”.
“txtsetup.sif” seems to be a file to customize the setup procedure. But where is this file? I can’t find it in the “setup disk”.
The windbg documentation is not fully relevant to vista/w2k8 installation.
You need the WAIK documentation and the WAIK itself.
Start here:
http://technet2.microsoft.com/WindowsVista/en/library/129a1712-e3d8-46c1-bc09-a14349dc67db1033.mspx?mfr=true
On Jan 10, 2008 10:37 PM, wrote:
> “txtsetup.sif” seems to be a file to customize the setup procedure. But
> where is this file? I can’t find it in the “setup disk”.
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
–
Mark Roddy
I find this valid link address:
http://technet2.microsoft.com/WindowsVista/en/library/129a1712-e3d8-46c1-bc09-a14349dc67db1033.mspx?mfr=true
But I can’t find any customization information about debugging setup. Should I download the tool "Automated Installation Kit "?
That is where I would start.
On Jan 11, 2008 5:05 AM, wrote:
> I find this valid link address:
>
> http://technet2.microsoft.com/WindowsVista/en/library/129a1712-e3d8-46c1-bc09-a14349dc67db1033.mspx?mfr=true
> ==========================================
> But I can’t find any customization information about debugging setup.
> Should I download the tool "Automated Installation Kit "?
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
–
Mark Roddy
I will come back while having results.
debug the same way you debug earlier releases except you have to use the
truly awful bcdedit to set up the debug options. Google ‘bcdedit windbg’ I’m
sure we have discussed this horrorshow at length.
On Jan 13, 2008 8:51 PM, wrote:
> I will come back while having results.
>
> —
> NTDEV is sponsored by OSR
>
> 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
>
–
Mark Roddy
Under Windows XP, I can modify txtsetup.sif as this:
OsLoadOptions = “/fastdetect /noguiboot /debugstop /debugport=com2 /baudrate=19200”
,and then I can debug the "copying files " and “formating partition” phases of installation. And you know, while at “copying files” and “formating partition” phases , the file “boot.ini” is not at the boot disk. So I think "txtsetup.sif " file is of much help.
And as for Vista, I should download “WAIK” first, and then I think I can do something useful. Because “bcdedit.exe” doesn’t exist on the boot disk while "formating disk " and “copying files”, so I think using “WAIK” is needed.
I have debugged "formating disks " and “copying files” phases successfully on XP by modifying txtsetup.sif .
Hi Mark Roddy,
WAIK really can custom the installation of Windows.
And we can just press “f8” to select the “debugging mode” of Vista’s installation. So easy.
Or we can run “setup.exe” on the Vista product DVD by transferring parametres “/debug …”.
Your ideas inspired me, helped me to reach my aim. My task is so urgent, and I must say "thank you " to you!
I would not combine /fastdetect with debugging options, this can lead to
serial port issues early in debug process (before boot drivers init and ntdll
load).
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
wrote in message news:xxxxx@ntdev…
> Under Windows XP, I can modify txtsetup.sif as this:
> OsLoadOptions = “/fastdetect /noguiboot /debugstop /debugport=com2
/baudrate=19200”
> ,and then I can debug the "copying files " and “formating partition” phases
of installation. And you know, while at “copying files” and “formating
partition” phases , the file “boot.ini” is not at the boot disk. So I think
"txtsetup.sif " file is of much help.
>