Black screen after boot.ini

[SV]

I'm running on a fixed 1GB Sandisk CF... But there is nothing except black
screen. No cursor, no status bar. I know its getting to boot.ini because I
put a dummy os option & timeout of 30s.
I got the pmq file from someone who started this project and left it for me.
I'm wondering if I should re-run tap and rebuild. I did put EWF in the
builds I've been testing, but I haven't tried to run FBA on another machine.
I put the build on an 800MB, active NTFS partition. But the same thing
happens on a 256MB fixed FAT/bootprepd CF (on active partition of 220MB).

Or maybe it's just taking an amazingly long time to run... Its a VIA chipset
with 256MB RAM.

Not sure whats next. TIA Shawna

 

[Slobodan Brcin \(eMVP\)]

Strange,

remove /noguiboot
or even better put /SOS switch in boot.ini.

You must see at least something if problem is not monitor related (someone
companied on TFT monitors or something like that recently).

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[SV]

I tried /SOS... no change

/noguiboot was never in the boot.ini file
I noticed there wasn't even a generic monitor, so I put in the montir

driver...

Same result!!

 

[KM]

SV,

Could you give us more info on the issue you are having?

Errors?
Steps you passed?
BSODs?

And it may be a good idea for ou to start the project from scratch running
TAP on the target device and do all the required steps then.

KM

 

[SV]

That's it... everything. No error messages... I upped the timeout in bootini
to verify it was getting there, which it did. I selected the os (only one)
and it goes to black screen. What is BSOD? I flashed the BIOS as per
manufacturer's file given to me a couple days ago. Nothing in the fba log -
none created.
I guess starting from scratch is pretty much all i can do at this point....

 

[KM]

SV,

That was not nothing. You saw the ntldr menu screen. This is good indication
that you have got a bootable system partition.
Make sure you have got a proper ARC path in your boot.ini to load OS
(although, if it were not correct you would see an error from ntldr).

BSOD - Blue screen of death.

You can try to coonect Kernel Debugger to your target instead of doing XPe
image from scratch. Although, I think the latter is better and easier for
you now.

KM

 

[Slobodan Brcin \(eMVP\)]

Although it is strange that ntldr is not throwing any status or error.

/SOS should show at least driver files that are loaded by ntldr in memory.
Having no indication is really strange, and I don't know what good creating
new image will bring.

SV,
Try making one entry in boot.ini to point to non existing ARC path, and try
to boot, you must get at least some error stating that there is no os.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[SV]

I did start from scratch and re- ran ta.exe on the target... I got a 7B blue
screen error from the image created with that new import file.
Then I booted from the XP PE CD and ran TAP. exe and still got 7B.
Then I re-ran TAP with a CF _in_ the CF slot, even though I wasnt using it
(just using CD ROM to boot at that point). and THAT allowed me to create a
bootable image!!

thanks again.