Jump to content











Photo
- - - - -

[Solved!] WimPack - Issues in LiveXP w/BootSDI Build


  • Please log in to reply
27 replies to this topic

#1 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 02 June 2008 - 06:49 PM

Downloaded today 'recommended' LiveXP (livexp server only); all settings default except:

1) Selected BootSDI (24MB free space) over CreateISO script.

2) Selected WimPack script (all settings as they default) and included req'd files at:
"%GlobalTemplates%\WimPack"
wimpackfiles.JPG

Build went well until WimPack script ran and 'hung' with 'UpdateExcludeFileList.exe' process pegging my CPU at 100%. After 45min. I attempted to end this process in taskmgr; after several attempts, got the following:
4_lx60208wp_fatalerr.JPG

and then:
5_lx60208wp_autoiterr.JPG

Even though I had made several attempts at shutting down WinBuilder, the build now continued with a BootSDI progress window and finally the ISO was created and successfully booted in Qemu! I was able to save a partial log which hopefully helps explain why wimgapi.dll is missing from "%BaseDir%\Projects\Tools\Wim" when the build wraps up:
Attached File  log.7z   109.23KB   248 downloads

#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 06:57 PM

Downloaded today 'recommended' LiveXP (livexp server only); all settings default except:

1) Selected BootSDI (24MB free space) over CreateISO script.

2) Selected WimPack script (all settings as they default) and included req'd files at:
"%GlobalTemplates%\WimPack"
wimpackfiles.JPG

Build went well until WimPack script ran and 'hung' with 'UpdateExcludeFileList.exe' process pegging my CPU at 100%. After 45min. I attempted to end this process in taskmgr; after several attempts, got the following:
4_lx60208wp_fatalerr.JPG

and then:
5_lx60208wp_autoiterr.JPG

Even though I had made several attempts at shutting down WinBuilder, the build now continued with a BootSDI progress window and finally the ISO was created and successfully booted in Qemu! I was able to save a partial log which hopefully helps explain why wimgapi.dll is missing from "%BaseDir%\Projects\Tools\Wim" when the build wraps up:
Attached File  log.7z   109.23KB   248 downloads

I have no knowledge about the WimPack stuff (I never tried before).
So I cannot add any helpful things to the issue.

But this again is a new proof of your title 'bug-catcher' ;)

Peter

#3 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 02 June 2008 - 07:45 PM

I have no knowledge about the WimPack stuff (I never tried before).
So I cannot add any helpful things to the issue.

But this again is a new proof of your title 'bug-catcher' ;)

Peter

Yes, I do seem to find them... (or maybe they find me) :thumbup:

:thumbup:

#4 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 June 2008 - 07:51 PM

Yes, I do seem to find them... (or maybe they find me) :thumbup:

Explain that at the bottom of your signature ;)

Peter

#5 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 03 June 2008 - 04:17 AM

Hi amalux,

I just saw this topic and have taken a look. I've uploaded a new version of the script which should take care of the wimgapi.dll issue. I'm not sure what's happening with UpdateExcludeFileList.exe. Test again and see if it's still occuring. It's probably not essential now that nikzzzz has expanded the features of WimPack.exe. You may disable it on the script interface.

Regards,
Galapo.

#6 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 03 June 2008 - 07:24 AM

Hi amalux,

I just saw this topic and have taken a look. I've uploaded a new version of the script which should take care of the wimgapi.dll issue. I'm not sure what's happening with UpdateExcludeFileList.exe. Test again and see if it's still occuring. It's probably not essential now that nikzzzz has expanded the features of WimPack.exe. You may disable it on the script interface.

Regards,
Galapo.

Thanks Galapo, will try the new script, with and w/out this option checked to see what happens ;)

#7 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 03 June 2008 - 10:17 AM

I just uploaded another new version which includes nikzzzz's new WimPack.exe released today. Able to organise a few things better because of this.

Regards,
Galapo.

#8 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10545 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 03 June 2008 - 10:33 AM

Thank you for updating! ;)

#9 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 04 June 2008 - 03:47 AM

I just uploaded another new version which includes nikzzzz's new WimPack.exe released today. Able to organise a few things better because of this.

Regards,
Galapo.

Hi Galapo,

Downloaded fresh and tried again; with 'UpdateExcludeFileList.exe' opton = same result as before.
With option unchecked, doesn't hang; no errors in log but bsod at boot w/ wimfltr.sys listed ;)
Attached File  log.7z   113.73KB   232 downloads

#10 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 04 June 2008 - 06:42 AM

Downloaded fresh and tried again; with 'UpdateExcludeFileList.exe' opton = same result as before.


Must have some problem with txtsetup.sif or your system doesn't like my AutoIt file...

With option unchecked, doesn't hang; no errors in log but bsod at boot w/ wimfltr.sys listed ;)


No idea why that is as I'm unable to reproduce it. Please try nikzzzz's WimPacker script and see if it has a similar result. May help us identify something.

Regards,
Galapo.

#11 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 05 June 2008 - 12:55 AM

OK, I've been able to isolate the issue with UpdateExcludeFileList.exe and have simplified things with it, so hopefully the bug is out of it now.

I'm still not able to reproduce the wimfltr.sys error. Are you still getting it? Do you get it with nikzzzz's WimPacker script too: http://www.boot-land...?...ost&p=36782.

Regards,
Galapo.

#12 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 05 June 2008 - 02:22 AM

OK, I've been able to isolate the issue with UpdateExcludeFileList.exe and have simplified things with it, so hopefully the bug is out of it now.

Thanks Galapo, I'll test the new script now and let you know.

btw, nothing else I've tried has worked but sometimes, if I end the UpdateExcludeFileList.exe process when it hangs and let the build finish, everything wraps up nice with no errors and a bootable ISO! When this is booted, it has the new WimPack drive present but empty. Other times I just get
bsod.JPG

Now I'll test that new script (with everything back to default settings) and let you know what happens ;)

...
I'm still not able to reproduce the wimfltr.sys error. Are you still getting it? Do you get it with nikzzzz's WimPacker script too: http://www.boot-land...?...ost&p=36782.

Regards,
Galapo.

I'm not sure what I'm supposed to do here, the download contains WimPack.exe which doesn't exist until WimPack.Script extracts it into //Tools/Wim (I assume the new WimPack.Script utilizes the correct .exe, so I'll ignore it) and WimPacker.Script, doesn't exist in LiveXP rec dl; is it supposed to replace WimPack or ???

#13 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 05 June 2008 - 03:02 AM

WimPacker script is Nikzzzz's version which doesn't have as many "features", the most significant being the lack of using a VMDK container. This means all WIM are loaded into the BootSDI ram image and consequently loaded into ram at boot. So the two scripts aren't meant to replace one or the other; they're just different scripts by different author's arising around the WimPack.exe program Nikzzzz has developed.

An idea: please post the version number of the wimfltr.sys you are using. I'm using 6.0.6001.18000.

Thanks for testing!

Regards,
Galapo.

#14 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 05 June 2008 - 03:17 AM

WimPacker script is Nikzzzz's version which doesn't have as many "features", the most significant being the lack of using a VMDK container. This means all WIM are loaded into the BootSDI ram image and consequently loaded into ram at boot. So the two scripts aren't meant to replace one or the other; they're just different scripts by different author's arising around the WimPack.exe program Nikzzzz has developed.

An idea: please post the version number of the wimfltr.sys you are using. I'm using 6.0.6001.18000.

Thanks for testing!

Regards,
Galapo.

New Rec-DL, all default except chk'd BSDI and WimPack scripts (both default) = No hang, no errors but same bsod w/ wimfltr.sys at boot. My version wimfltr.sys is differant! 6.0.6000.16386 (how much you wanna bet that's the problem?) makes sense, I'm an ideot; I ass-umed it was the same version WAIK ;) It'll take me awhile to download the new version and test but I'm sure that's it. Sorry to waste your time.

Thanks Galapo :thumbup:

#15 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 05 June 2008 - 03:24 AM

No, don't be sorry. This helps to catch the problems. If it turns out to be related to the file version, then I need to adjust the script to make a check of this.

Regards,
Galapo.

#16 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 05 June 2008 - 05:54 AM

Strange, I've just finished testing with 6.0.6000.16386 files, with the same constellation of scripts as you, and still can't get a BSOD.

Anyway, see how your tests go.

Regards,
Galapo.

#17 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 05 June 2008 - 06:02 AM

Strange, I've just finished testing with 6.0.6000.16386 files, with the same constellation of scripts as you, and still can't get a BSOD.

Anyway, see how your tests go.

Regards,
Galapo.

Yes, it is strange indeed. I've just tested with the new files and it booted OK in Qemu (no desktop wallpaper ;) ), even shows the .wim's in Z: but still won't boot from CD :thumbup:

Tried two runs, just to make sure but same thing, gets to 'Setup is inspecting computer hardware...' then re-boots. My current conclusion is :thumbup:

#18 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 05 June 2008 - 06:15 AM

Can you try a 2k3 build to see if that makes any difference for you?

Thanks,
Galapo.

#19 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 05 June 2008 - 08:00 AM

Can you try a 2k3 build to see if that makes any difference for you?

Thanks,
Galapo.

Well, it's different ;) A few errors in the log but nothing serious... loads to RAM OK and seems to start-up but just gets stuck at 'Please wait...' (Qemu and real).

Tired now, I'll play with it more tomorrow. Thanks again for your help Galapo :thumbup:
Attached File  log.7z   123.25KB   180 downloads

#20 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 05 June 2008 - 11:31 PM

Hi amalux,

Did a bit more testing. Downloaded LiveXP "recommended" so we're starting with exact the same files. Pointed WimPack to necessary files, same with BootSDI as I built with XPsp2. Qemu booted completed build fine. I'm really not sure why you're not getting the same.

Regards,
Galapo.

#21 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 06 June 2008 - 12:41 AM

Hi amalux,

Did a bit more testing. Downloaded LiveXP "recommended" so we're starting with exact the same files. Pointed WimPack to necessary files, same with BootSDI as I built with XPsp2. Qemu booted completed build fine. I'm really not sure why you're not getting the same.

Regards,
Galapo.

Like I said, it's ;) I'm gonna keep testing.

Thanks Galapo :thumbup:

#22 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 June 2008 - 12:52 AM

I'm just uploading a new version now. I made a coupe of changes. Give it a go and see if it makes any difference.

Thanks,
Galapo.

#23 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 06 June 2008 - 05:33 AM

Hi amalux,

Did a bit more testing. Downloaded LiveXP "recommended" so we're starting with exact the same files. Pointed WimPack to necessary files, same with BootSDI as I built with XPsp2. Qemu booted completed build fine. I'm really not sure why you're not getting the same.

Regards,
Galapo.

OK, first I want to make sure we're clear on something; even with previous builds I was able to boot in Qemu but when that same ISO was burned to CD, I could not get past the 'Please wait...' (waited at least 10 minutes each time). Sorry if I didn't make this clearer in my posts. Now, on to the latest build...


I'm just uploading a new version now. I made a coupe of changes. Give it a go and see if it makes any difference.

Thanks,
Galapo.

Yes! It works!! :thumbup:

I don't know what you changed but it works great now! I did a second run to be sure it wasn't a fluke and that worked as well. I even went back to the previous build (that didn't work) and ran it again just to confirm and same as lst time, booted OK in Qemu but not from CD. So this confirms some change in the last download (for some reason I think you're going to tell me you made no change and this is just a 'placebo' thing but, if so, it defies the evidence) Either way, I'm glad it's working now and I can start having fun with it! Thanks again for the awesome work and for all your help! :thumbup:

:thumbup:

---
btw, hardly worth mentioning but just so you know, everything is working fine in the booted projects (programs work; .wim's in Z: look good etc.) except one thing, oddly, the 'Wallpaper' script which has always worked fine in past projects now just gives me a grey desktop :thumbup:
qemugrey.JPG

I know the Wallpaper script hasn't changed so it must be a conflict with WimPack (or some other change in the LiveXP download since we started these tests (it's done this on every build since starting this topic; Qemu and real boot i.e the ones that booted at all). Unless you have an idea what this is I'll just start a separate bug report; I don't want it to take away from the success here which is far more important ;) Thanks again buddy!

#24 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 June 2008 - 06:13 AM

So this confirms some change in the last download (for some reason I think you're going to tell me you made no change and this is just a 'placebo' thing but, if so, it defies the evidence) Either way, I'm glad it's working now and I can start having fun with it!


Don't worry, there's a significant change allright. This line
If,NotExistFile,"%target_sys%\drivers\wimfltr.sys",FileCopy,"%pFileBox1%\wimfltr.sys","%target_sys%\drivers"
was changed to
FileCopy,"%pFileBox1%\wimfltr.sys","%target_sys%\drivers"

The problem was that an updated wimfltr.sys wasn't being copied. Oddly, my XPsp2 source must have a version of wimfltr.sys that is OK so my system wasn't getting the BSOD.

Now, the wallpaper issue I'll take up with Nikzzzz. Currently, they would be getting shifted into the system WIM image. Either Nikzzzz will need to get WimPack.exe to update the registry to point to the changed path or we'll need to specify that (desktop) image(s) remain in \system32\.

Regards,
Galapo.

#25 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 06 June 2008 - 06:39 AM

I've uploaded a new version which will take care of the wallpaper issue. Images if present will remain in \system32\. If Nikzzzz adds the feature into WimPack.exe to alter the registry to reflect the changed path, I can alter the script back so that images will be copied into the WIM again.

Regards,
Galapo.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users