OfflineSysPrep (Page 1 of 2)

Thanks Galapo!  Your tool comes in really handy to me.

I have a question for you about the MassStorage builder that is included with the BartPE plugin.  I noticed that the latest RC of DriverPacks BASE has a little different of a setup now for the plugin where the "BASE.inf", "MassStorage.inf", and "MassStorage.sif" are no longer at the root of the DriverPacks plugin folder.  When I try to run the MassStorage builder, it can't find the DriverPacks plugin.  Is there any way that the MassStorage builder could be updated to look what the current official release of DriverPacks BASE does for setup of the MassStorage plugin as well as what the latest RC of the DriverPacks BASE does for the setup of the MassStorage plugin?

Thanks for the report.

Sorry for the delay -- I've been on holidays and away from internet access. The latest BartPE plugin and WinBuilder scripts now contain an updated CreateMassStorageData.exe which should fix the issue (providing Overflow doesn't alter the location of MassStorage.inf again).

Also, I've updated the LiveXP mass storage driver script for the same issue in case a user supplies a newer BASE.

Regards,
Galapo.

Congratulations on the new release! And Merry Christmas and happy New Year to you also. My holiday was great, we even had baby sitting at times since my parents also rented a unit in the same block as us! I hope you get a relaxing break some time too.

Regards,
Galapo.

Generally developers do not like documenting and writing help files. And this is true of OfflineSysPrep. It assumes familarity with the processes it provides a "front-end" for. Development is done in my spare time, which is limited, and so help file stuff is limited because it is not fun to do. I'm sorry, I wish I had more time.

Generally, the error that you got is due to using some other program named "runscanner" rather than the one that should be used from here.

Hope this helps.

Regards,
Galapo.

Read 1st post, carefully this time.

Read BEFORE you post  HWID's Tool  DriverPacks tutorial  DriverForge & FindHWIDs



Donate!

The w2k code was unfortunately removed quite a while ago. It's still there in that older version, which I could revisit if there was a need and add support into the newer version. What would do it for me I guess would be if my w2k machine packed it in and I had to upgrade the motherboard ... but I hope that doesn't happen!

If I get some time later in the year I can revisit the issue though.

Regards,
Galapo.

Update, the MX3228 came to life after a reboot.  The first time through the setup the mouse and keyboard do not respond and plugging in a USB mouse will not detect it.  After a forced shutdown all peripherals are working and I can continue.

Ian

Oh, and "fix possible keybosrd/mouse unresponsiveness" WAS selected......can't BELIEVE I forgot to mention that the first time around!! 

Last edited by llewxam (2009-03-24 10:38:54)

Another system has come up with a problem, Dell Dimension 5150.  After putting the image on the system booted, XP splash screen preparing to show the blue "XP is preparing to start" screen, but the blue screen never came, just a nasty restart.  It then took me to a Boot Menu which I knew was a bad sign.  Reimaged and tried again, same result.  I reimaged, let the image install on another computer, then used OSP with no HAL switch (both machines are ACPI multi), did MS injection and SID generation.  Put the drive back in the Dell, another nasty restart.  I let it boot to Safe Mode, it got to a black screen with the mouse cursor, USB Mouse and keyboard (all that POS has) were frozen but did wake up, but Safe Mode never fully booted.  After a few minutes of no activity from the HDD I was considering shutting it down, but it then suddenly restarted itself, and was then able to boot normally.

Any other info that would be helpful, let me know.  I'll grab HWIDs while I can, this is a rush service job so I can't hold on to the machine...

Ian

I have put my image with OSP on many many machines by now, and am noticing that the HAL detection on first boot is a very common place to hang.  It mainly happens on older hardware but there have been some more modern systems that I really thought it should work on, but the amount of hangs I have had with OSP is more than I was expecting.  Even many 478 P4 systems are not taking my OSP image, and I don't want to have to have multiple images, that kinda defeats the point.  Of course, your HAL detect on next boot is a new feature, but I was wondering how many other reports of this you are getting?

My current method is use SysPrep to reseal with no MS integration, then OSP (I updated to 1.10.0.6, no improvement) in Windows with the target as slave, to integrate MS.  I am considering a switch back to MySysPrep for HAL detect, I had no issues whatsoever with it's HAL detection but just hated the flashing banner in the top right of mini-setup.  I'd still use OSP for MS integration.

So I guess my point, and question, is that the HAL detect seems a bit shaky as-is, and I was wondering if you have more tweaks you wanted to implement in to the HAL detection that may make it more reliable, or if it is working flawlessly for tons of other people and I have something else screwing it up........

BTW I can move my questions to 911CD or whichever other forum you want if you prefer......

Thanks!

Ian

WOW, you better be getting well compensated for a situtation requiring you to go through a move like that!!!

I forgot to mention in my previous post, I Ghosted my original installation after SysPrep only, so it is very quick and easy for me to play around with OSP, and I did make a test image using ALL of the same settings as the problem image, except Do Nothing for HAL detect, and machines were able to boot with that change, so that is definately my issue....

I will try to help you as much as I can with the HAL issue.  What I will do from now on is on any machine that my HAL-switch OSP image bonks, I will write down the model number of the motherboard, and then put on my non-HAL-switch OSP image which has standard ACPI HAL, then try changing the HAL to uni and Standard PC, and see if I can narrow down HALs that don't work.  While I am not sure yet how to automate this or do any kind of detection, I do have access to a lot of different hardware so maybe something can come out of this....  Besides, I'd need to use the non-switch image anyway to get the machine running, might as well check...

Ian

Any chance we could see a "set HAL interactively on next boot" option?  I still want to try setting manually on a few systems, just a thought that came to me a moment ago....

Ian