Jump to content











Photo
- - - - -

Preloader Error during Boot


  • Please log in to reply
15 replies to this topic

#1 DaveWa

DaveWa

    Newbie

  • Members
  • 18 posts
  •  
    Germany

Posted 28 December 2009 - 04:45 AM

I tried to create a boot CD with WinBuilder 078 SP4 and VistaPE CAPI v.12. During running the scripts I did not get any error message.
During booting from CD I get an error message from Preloader.cmd "Windows-no Volume" (see attached jpg)

Does anybody has an idea what the reason for this behaviour is?

Regards
DaveWa

Attached Thumbnails

  • Preloader_Error.jpg


#2 JonF

JonF

    Gold Member

  • .script developer
  • 1185 posts
  • Location:Boston, MA
  •  
    United States

Posted 28 December 2009 - 01:34 PM

I tried to create a boot CD with WinBuilder 078 SP4 and VistaPE CAPI v.12. During running the scripts I did not get any error message.
During booting from CD I get an error message from Preloader.cmd "Windows-no Volume" (see attached jpg)

Does anybody has an idea what the reason for this behaviour is?

Hum. There is probably some drive that is reporting as ready but really isn't ready. What drives do you have on that system?

#3 DaveWa

DaveWa

    Newbie

  • Members
  • 18 posts
  •  
    Germany

Posted 28 December 2009 - 02:27 PM

Hum. There is probably some drive that is reporting as ready but really isn't ready. What drives do you have on that system?


Please see attached file.

I did not have this effect when I used WinBuilder 078 SP2 and VistaPE CAPI v.12 (data downloaded three month ago).

Attached Files



#4 JonF

JonF

    Gold Member

  • .script developer
  • 1185 posts
  • Location:Boston, MA
  •  
    United States

Posted 28 December 2009 - 07:57 PM

The preloader wwas added recently.

I will have to set up a debug version for testing. It may take me a day or two.

#5 JonF

JonF

    Gold Member

  • .script developer
  • 1185 posts
  • Location:Boston, MA
  •  
    United States

Posted 30 December 2009 - 01:37 PM

I will have to set up a debug version for testing. It may take me a day or two.

OK, try this version of 07-config. I may have found a bug, so it may work. If it still fails let me know that the last line on the screen is.

#6 DaveWa

DaveWa

    Newbie

  • Members
  • 18 posts
  •  
    Germany

Posted 31 December 2009 - 02:13 PM

OK, try this version of 07-config. I may have found a bug, so it may work. If it still fails let me know that the last line on the screen is.


Setting Locale to "German" in Main Configuration works now, also setting to "Auto" works!

The Preloader Error no longer occurs. But at the end of starting VistaPE I get a message "found new configuration.." (see attachement "new configuration.jpg"). There is no differnce whether I click yes or no. All my links from the start menü or desktop rever to drive R butdo not work. When I go to drive R in the explorer and click there, I get the messege "insert a disk" (or similar). The VistaPE CD with the programms is now in Drive D (see attachement "Drives new.jpg"). In the older versions it worked well ( see attachement "Drives old.jpg").

Attached Thumbnails

  • new_configuration.jpg
  • Drives_new.jpg
  • Drives_old.jpg


#7 JonF

JonF

    Gold Member

  • .script developer
  • 1185 posts
  • Location:Boston, MA
  •  
    United States

Posted 01 January 2010 - 02:16 PM

That's strange. OK, try this version.

#8 DaveWa

DaveWa

    Newbie

  • Members
  • 18 posts
  •  
    Germany

Posted 02 January 2010 - 03:01 PM

That's strange. OK, try this version.

John,

I did some tests with the new version 18 of 07-config.script. I do not understand what is going on there; therefore I will explain it a little bit more in detail:

I have two hard drives. First drive with primary partition C, and logical drives D to L (in Windows Vista).
Second hard drive (named “Platte_2”) with one primary partition M (in Windows Vista).
Two CD-Drives.
When I did the first test end of October 2009 I used version 16 of 07-config.script (Date=29 Aug 2009). I do not know whether another script also influences the behavior I will explain later.

The VistaPE CD I created worked (with exception of keyboard settings to German). The structure of the drives is shown in the first picture. CD drives in PE were Q and R. VistaPE CD was in Q and also all desktop and start menu links refer to Q. That means all the links worked. Drive R was empty (no CD in)

With the new version 18 of 07-config.script (and perhaps other scripts influence this, what I do not know) I have the following effect:
1-VistaPE CD is put in the first CD Drive:
After VistaPE loading is finished, I get the message: “found new configuration file d: vistape.cfg. Do you want to rebuild icons?” Pressing yes or no does not lead to different behavior. In the VistaPE explorer the VistaPE CD is now shown in Drive D (see second picture). All desktop and start menu links refer to Drive R. In that case the links of course do not work because VistaPE CD is in Drive D and second CD Drive R is empty. But if I put a CD in Drive R (the CD has nothing to do with Vista PE, it was the Windows AIK Setup CD), and click a link which refers to R, the link will work. When I make a right click on the icon on the desktop to look at the properties, now the link refers to Drive D and no more to Drive R!

2-VistaPE CD is put in the second CD Drive:
The same message regarding the new found configuration file (I cannot remember where this file was located). In the VistaPE explorer the VistaPE CD is now shown in Drive R (see third picture). All desktop and start menu links refer to Drive Q!! Please notice that Drive Q is my second hard drive “Platte_2”!!. In that case the links of course do not work because VistaPE CD is in Drive R (second CD Drive D is empty). But if I put a CD in Drive D (the CD has nothing to do with Vista PE, it was the Windows AIK Setup CD), and click a link which refers to Q (second Hard Drive “Platte_2”!!. ) , the link will work. When I make a right click on the icon on the desktop to look at the properties, now the link refers to Drive R and no more to Drive Q!

Can you understand what is going on there?

Attached Thumbnails

  • Drives_old.jpg
  • Vista_PE_Drive_D.jpg
  • Vista_PE_Drive_R.jpg


#9 allanf

allanf

    Gold Member

  • .script developer
  • 1256 posts

Posted 02 January 2010 - 03:12 PM

... :) ...

Forgive me for laughing! What a bizarre story! And you've done very well to explain it. ... :) ...

I hope there is an equally entertaining solution.

Regards :)

#10 JonF

JonF

    Gold Member

  • .script developer
  • 1185 posts
  • Location:Boston, MA
  •  
    United States

Posted 02 January 2010 - 09:50 PM

I'll have to think about this some. I suspect a script interaction or some change in your system. The most recent version of 07-config that you tested has no preloader and the loading operates exactly the same as version 16.

#11 DaveWa

DaveWa

    Newbie

  • Members
  • 18 posts
  •  
    Germany

Posted 03 January 2010 - 07:52 AM

I'll have to think about this some. I suspect a script interaction or some change in your system. The most recent version of 07-config that you tested has no preloader and the loading operates exactly the same as version 16.

Perhaps there is a script interaction. There should be no changes in the system. I cannot remember that I changed anything during the last year.
But I remember a similar behavior with an older version of Acronis True Image and this hardware configuration. The Acronis Rescue CD only worked when there was a CD (no specific CD necessary) in the second CD-Drive.

#12 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 03 January 2010 - 04:19 PM

Hello

With error in original post….

I have seen that error message before; I think it had to do with selecting Shells or a default shell

I cant remember what I did, nor can and I reproduce that error again,,

EDITED -
This is just for me Preloader works better when more than one shell is selected
in Main Configuration i left default shell as explorer under base i also selected BS Explorer
bult no errors, booted no errors

this was done with a clean load - just downloaded, just built - (tested in VMware)

#13 DaveWa

DaveWa

    Newbie

  • Members
  • 18 posts
  •  
    Germany

Posted 03 January 2010 - 06:09 PM

This is just for me Preloader works better when more than one shell is selected
in Main Configuration i left default shell as explorer under base i also selected BS Explorer
bult no errors, booted no errors

this was done with a clean load - just downloaded, just built - (tested in VMware)

When you selected BS Explorer did you also activate "Add to PE Shell"?

#14 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 03 January 2010 - 06:12 PM

yes that was selected by default,, so was add shortcut to desk top

hope this helps...........

when booted in VMware ,, it still defaulted to Explorer desktop

Remember this was done with only one change after download all default settings
that was selecting or checking BS Explorer under Base before build

now i will try unchecking BS Explorer and build again,,

#15 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 03 January 2010 - 06:55 PM

There is something not right, with my 3 build (Not changing a thing) it could no longer read my source files,, i reselected same source and 4th build went fine

I first thought it was my source files or Vista folder, i havent built a Vista Pe in days , but after reselecting source it work again built fine tested in Vmware.

Maybe some one else will have some ideas

PS: BS Explorer was not selected with last build and it built fine, all default settings

#16 DaveWa

DaveWa

    Newbie

  • Members
  • 18 posts
  •  
    Germany

Posted 08 January 2010 - 03:32 AM

I'll have to think about this some. I suspect a script interaction or some change in your system. The most recent version of 07-config that you tested has no preloader and the loading operates exactly the same as version 16.

John,

do you have already an idea what the reason could be for this behaviour I described in posting Post #8 ?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users