D
Dave August
I've built what I though would be a bootable image, (and yes it does boot
after I got the dreaded Stop 7B and manually added both IDE channels)... I
didn't specify my app just the command shell. I naively assumed that it
would boot and run and even give me a task bar, but not have any apps except
the shell... And yes I resolved all dependencies, and yes I got the basic
system info from TA not TAP...
Well... it boots, showsthe splash screen, shows the blue background with a
working mouse, then a quick flash of a status dialog that I *think* says
"Initializing components" and then.... reboots... <sigh> .... So OK what
Newbie thing have I missed? Do I really need to specify some app? An how
the heck do you guys debug this stuff.. in DDK land we'd hook up the Kernel
Debugger and have SOME clue... which brings up an interesting question, if
I stick the debug stuff in boot.ini will this thing spew any valid info to
KD or WinDebug (and do I have to build for Debug to get it) ? ....
Dave (the newbie in the dark)
after I got the dreaded Stop 7B and manually added both IDE channels)... I
didn't specify my app just the command shell. I naively assumed that it
would boot and run and even give me a task bar, but not have any apps except
the shell... And yes I resolved all dependencies, and yes I got the basic
system info from TA not TAP...
Well... it boots, showsthe splash screen, shows the blue background with a
working mouse, then a quick flash of a status dialog that I *think* says
"Initializing components" and then.... reboots... <sigh> .... So OK what
Newbie thing have I missed? Do I really need to specify some app? An how
the heck do you guys debug this stuff.. in DDK land we'd hook up the Kernel
Debugger and have SOME clue... which brings up an interesting question, if
I stick the debug stuff in boot.ini will this thing spew any valid info to
KD or WinDebug (and do I have to build for Debug to get it) ? ....
Dave (the newbie in the dark)