The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 807 - File: showthread.php PHP 7.3.15 (Linux)
File Line Function
/showthread.php 807 errorHandler->error

Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Blank screen when wimboot starts
2013-11-25, 15:50 (This post was last modified: 2013-11-25 16:08 by Snowbird.)
Post: #1
Brick Blank screen when wimboot starts
Hello Everyone,

I recently wanted to install Win 7 using Robin's scripts located here :
First, I would like to thank you for sharing all this stuff !! Smile that was very useful to me and probably for many others.

So back to my problem, I'm having problems with winboot that doesn't want to execute, I get a blank screen whenever I reach this final step in the boot process.

here's an excerpt of what I am trying to make work :
echo Starting Windows 7 ${arch} installer for ${initiator-iqn}

# Force gateway to be the iSCSI target server (kludge for stupid window behavior)
set netX/gateway ${iscsi-server}

# Hook iSCSI drive
set root-path ${base-iscsi}:${hostname}.boot.windows7
sanhook ${root-path} || goto failed

# Start Windows 7 installer DVD
#sanboot --no-describe --drive 0x81 ${sanboot-url}windows-7/ultimate-${arch}-en.iso || goto failed
# Better solution, according to Oliver Rath on the mailing-list
# Requires massive amounts of RAM, though
#initrd windows-7/ultimate-${arch}-en.iso
#chain memdisk iso raw || goto failed

# This method uses wimboot
set base-url windows-7/ultimate-${arch}-en
kernel wimboot
initrd ${base-url}/bootmgr                     bootmgr
initrd ${base-url}/boot/bcd                    BCD
initrd ${base-url}/boot/fonts/wgl4_boot.ttf    wgl4_boot.ttf
initrd ${base-url}/boot/boot.sdi               boot.sdi
initrd ${base-url}/sources/boot.wim            boot.wim
boot || goto failed
goto start

Everything goes smoothly, as you can see in the syslog screenshot below :

[Image: birm1v.png]

and when it reaches the step where it needs to launch wimboot I get a blank screen right after the screenshot below :

[Image: osbtqx.jpg]

I have read on this forum that I have to wait sometimes for a long time, well even after 30 minutes of wait nothing happens, still blank screen... After doing some investigations, I noticed that the network connection gets lost about 2 seconds after the attempt of launching the wimboot file, and never comes back... My NIC is a : RTL8111E (if it helps)

Does anyone ever solved this problem, because I've seen many people here on this forum having the exact same problem, but with no solution, I'm guessing it's a bug that needs to be addressed, or maybe I'm doing something wrong...

Any help or idea is welcome Smile


Oh I forgot to tell you something important, if I disable only this one line by commenting it :

#sanhook ${root-path} || goto failed

(means I don't hook anything)

The Windows 7 installation process loads, and I'm able to run the installation normally ! all this happens in less than 10 seconds (so it's very fast), of course I can't install it on the my san target since I didn't hook it in the first place... This is a really strange behavior.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
Blank screen when wimboot starts - Snowbird - 2013-11-25 15:50

User(s) browsing this thread: 1 Guest(s)