I've tried creating a full VPE and a minimalist VPE through version 011 with the USB Device option, but when I boot to the USB Device I get grub, choose VistaPE, it does the loading bar and then goes to a black screen with only the cursor. The cursor is usable, but nothing else ever happens. Any ideas?
Nevermind: Found the post from 008.
Black Screen and Cursor only (VPE 11)
Started by
gomjh
, Jan 20 2008 12:24 AM
8 replies to this topic
#2
TheHive
-
- .script developer
-
- 4202 posts
Platinum Member
Posted 20 January 2008 - 01:43 AM
Can you provide a cross reference link to the post you found. Thanks!Nevermind: Found the post from 008.
#3
Talven81
-
- Members
- 4 posts
-
United States
Posted 24 January 2008 - 12:09 AM
Yes I read the 008 thread and searched the forum, however this is a persisting issue in 011 and I was able to find no resolution to using the boot.wim
It seems to be an issue with building VistaPE using the option "Build Model: In RAM (boot.wim)" when building "Normal" it seems to work fine. This is an issue that has persisted since previous versions and would be nice if it was fixed.
I must have the boot.wim method since I am building diagnostics setups for my work and will be booting off both CD and flash drive. While booting from the CD the "Normal" method is OK, however with flash drive the boot.wim is required.
Has anyone found a work-around for this?
It seems to be an issue with building VistaPE using the option "Build Model: In RAM (boot.wim)" when building "Normal" it seems to work fine. This is an issue that has persisted since previous versions and would be nice if it was fixed.
I must have the boot.wim method since I am building diagnostics setups for my work and will be booting off both CD and flash drive. While booting from the CD the "Normal" method is OK, however with flash drive the boot.wim is required.
Has anyone found a work-around for this?
#4
MedEvil
-
- .script developer
-
- 7771 posts
Platinum Member
Posted 24 January 2008 - 12:16 AM
Boot.wim can only be build, if you have Waik installed and setup in build\0-preconfig.It seems to be an issue with building VistaPE using the option "Build Model: In RAM (boot.wim)" when building "Normal" it seems to work fine. This is an issue that has persisted since previous versions and would be nice if it was fixed.
Has anyone found a work-around for this?
#5
gomjh
-
- Members
-
- 18 posts
Newbie
-
United States
Posted 24 January 2008 - 03:44 AM
I had the Winbuilder folder in C:\Users\username\documents\WinBuilder
I moved it to C:\WinBuilder and rebuilt the VistaPE key and the issue disappeared.
I moved it to C:\WinBuilder and rebuilt the VistaPE key and the issue disappeared.
#6
Pavel Azanov
-
- Members
-
- 32 posts
Member
-
Germany
Posted 24 January 2008 - 08:05 AM
I had the same problem first (Black screen with a cursor and nothing else). Try to set the bootmanager to standard and do not pack the boot.wim. The iso will be much bigger but finally it worked for me.
#7
MedEvil
-
- .script developer
-
- 7771 posts
Platinum Member
Posted 24 January 2008 - 01:40 PM
Seems the path got to long for some program to handle.I had the Winbuilder folder in C:\Users\username\documents\WinBuilder
I moved it to C:\WinBuilder and rebuilt the VistaPE key and the issue disappeared.
#8
Talven81
-
- Members
- 4 posts
-
United States
Posted 24 January 2008 - 06:50 PM
Hmm so far no successful answer to my problem.
I know that a UFD can be built using the boot.wim, our client engineering team here at work has successfully built a deployment system for WinXP based on WinPE 2.x however they are not forthcoming when asking them questions regretfully.
In reply to the above:
#4: The boot.wim is builing "fine", I am just getting no shell on boot. WAIK is installed properly and working.
#5: Yes found the path name problem back when I was building WinPE 1.0 (xp base) stuff. WinBuilder is located in C:\WinBuilder\
#6: Please go back up and read my post, I need the boot.wim since I am booting off of a UFD (flash drive) as well as CD, both need to be available for the environment it will be used in.
By the way I am building this in an XP environment, testing in VMWare, CD boot, and UFD boot.
So far no resolution to this issue, keep 'em coming guys. I appreciate the feedback.
(PS if the resolution you provide is listed in the 008 post, please don't bother here.)
I know that a UFD can be built using the boot.wim, our client engineering team here at work has successfully built a deployment system for WinXP based on WinPE 2.x however they are not forthcoming when asking them questions regretfully.
In reply to the above:
#4: The boot.wim is builing "fine", I am just getting no shell on boot. WAIK is installed properly and working.
#5: Yes found the path name problem back when I was building WinPE 1.0 (xp base) stuff. WinBuilder is located in C:\WinBuilder\
#6: Please go back up and read my post, I need the boot.wim since I am booting off of a UFD (flash drive) as well as CD, both need to be available for the environment it will be used in.
By the way I am building this in an XP environment, testing in VMWare, CD boot, and UFD boot.
So far no resolution to this issue, keep 'em coming guys. I appreciate the feedback.
(PS if the resolution you provide is listed in the 008 post, please don't bother here.)
#9
Talven81
-
- Members
- 4 posts
-
United States
Posted 24 January 2008 - 07:05 PM
Scratch that! Resolution found!
See this post, it didn't come up in my previous searches... apparently it's a WinBuilder directory permission issue.
http://www.boot-land...?showtopic=2889
See this post, it didn't come up in my previous searches... apparently it's a WinBuilder directory permission issue.
http://www.boot-land...?showtopic=2889
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
