• 0

How can I use sysprep with different processors?


Question

I have 3 versions of the Panasonic Toughbook CF-30. Each version has a slightly newer Intel Centrino Duo processor. I use ghostcast and sysprep to image them all. My problem is that I have to maintain 3 separate images because I get a BSOD if I don't match the computer with the right image. I would think since they're all CF-30's I should be able to make one image for all of them. Even if I sysprep it still BSOD.

I've tried the program UIU and it doesn't blue screen but it doesn't have the drivers needed and asks me for a whole bunch of during setup. Then I have to install all of the drivers once booted. Hardly saving me time.

Is there anyway I can use drivermax (http://www.innovativ....com/drivermax/) to extract drivers from all 3 systems and place them in a folder and point my sysprep.inf there. I read that there is a sysprep command but will sysprep seek out the drivers in subfolders or do I need to point each device to a folder?

Here is a link I found but I don't know what to do with it.

http://www.panasonic...build.asp#CF-30

To me the most simplist way would be to put the three processor drivers in a folder and have sysprep find which one fits when the build boots but I have no idea how to make it happen. Thank you for looking.

Edit*

I should mention I'm using Windows XP and I found the Processor information

74947332.png

10 answers to this question

Recommended Posts

  • 0
  On 23/04/2012 at 18:26, SSF said:

My fault. I left out that I'm using Windows XP due to legacy software :(

Ok, I will check and see what I can find on that. :)

EDIT: Maybe this one will help. http://community.spiceworks.com/how_to/show/2036

  • 0
  On 23/04/2012 at 18:37, SSF said:

I don't see how I get BSOD with three dual core processors. Am I missing something?

I guess I misunderstood your request. I was under the impression that you were looking for a tutorial on how to create the single image for multiple systems. Is that correct or incorrect? :s lol

  • 0

Yes that's right. From my understanding there is two HAL's. One is one core processor and the other is multicore. So if I had a bunch of different computers but they all had dual core processors and they were sysprep'd then why would it blue screen.

  • 0
  On 23/04/2012 at 18:59, spikey_richie said:

Is the ONLY difference the CPU? Chances are they chipset maybe slightly different, or there's some discreet device which is being depended upon for boot...

I'm sure it's not the only difference. I might try the suggestion winlonghorn said here http://community.spiceworks.com/how_to/show/2036 and use drivermax to extract drivers from all 3 images.

  • 0

XP sysprep doesn't remove the HAL information, windows 7 sysprep does. You would need to perform a universal restore, but you are doing that if you need to reinstall drivers and such which is hardly saving you any time (really it saves you a bunch as all you have to do is reload drivers not individual apps or updates).

You could write a script to run after initial install to update drivers this would then save you the hassle of doing it manually. You can manually execute the script so you can have the specific drivers added for the specific machine after image has taken place.

  • 0

^ What he said. Sysprep before Windows Vista isn't HAL-independent. That was the BIG improvement with Vista. You can try Universal Imaging Utility for Windows XP which works just as well.

This topic is now closed to further replies.
  • Posts

    • It's become a central place at my workplace. I use it for meetings, general chatting between employees, and the teams for storing of files to share between people at work. 
    • It's a Dell color laser printer. Back when Microsoft kept having these security flaws with the print spooler and recommending you disable it I just got in the habit of it, and I use it so rarely now I just leave it disabled in case another flaw pops up.
    • KDE makes progress toward full Wayland session restore in Plasma 6.5 by David Uzondu In the latest issue of This Week in Plasma, the development team, as usual, brings news of ongoing work for the desktop environment. While KDE continues to polish the recently released Plasma 6.4, work has already taken off on the next major version of Plasma, 6.5. A significant step forward is being made on Wayland session restoration; the xx-session-management-v1 restore protocol has been implemented in Qt 6.10, which means KDE applications and Plasma itself can soon start using it to finally bring proper session restore to Wayland. For more immediate user-facing changes in Plasma 6.5, the Welcome Center application now teaches you about the many available keyboard shortcuts, as well as "what the heck the 'Meta' key is." For those who frequently work remotely, Plasma's built-in RDP server now supports syncing clipboard text between the client and server. The clipboard also received another useful feature, letting you copy the QR code for an item, not just view it. The team is also addressing smaller usability issues across the desktop, including fixes that will land in point releases for Plasma 6.4. Spectacle, for example, will no longer show a ghostly semi-transparent version of its menus in screenshots. The New! badge, which was introduced in Plasma 6.4 is now easier to read with better colors. Other notable UI improvements include: A new button on the "missed notifications" pop-up that lets you view what you actually missed. The Networks widget is now much better at telling you what it is doing, like when it is "looking for wireless networks". Inertial scrolling with touchpads is now active in all QtQuick-based KDE software. As always, the KDE team spent the week squashing bugs across various versions of Plasma and related software. Plasma 6.4.1, which went live this Tuesday, addressed several crashes in the desktop portal implementations and patched the open/save dialog, where apps could insert extra UI elements in the wrong places. It also resolved a recent performance regression affecting some games and fixed a strange issue with drawing tablets where the pointer could disappear when two were connected in different modes. 6.4.1 tackled a particularly odd hardware-specific problem with Samsung Odyssey G5 monitors endlessly turning on and off because of a faulty DDC implementation. KDE responded by blacklisting the device. In addition to that, the update fixed an accessibility regression in Discover, corrected an issue where deleting a favorited app left behind a ghost item you couldn't un-favorite, and restored the Window List widget's ability to minimize windows. As for fixes planned for 6.4.2, here's the full list as outlined by the Plasma team: Fixed a case where System Settings' Flatpak App Permissions page could cause the whole app to crash. Fixed an issue that could sometimes cause Plasma to go back to sleep again right after waking up, when the "Sleep then hibernate" setting is in use. The appearance of text labels in Folder View pop-ups is once again correct. You're no longer erroneously prompted to authenticate for a Wireguard VPN whose credentials are already stored in KWallet, and the wallet is set up to automatically open at login. Fixed an issue in the KDE desktop portal's screenshot implementation that prevented the delay setting from taking effect. Missing app backends listed in Discover's Settings page once again show the correct names. The brightness level shown on System Settings' Display & Monitor page now matches the one shown in Plasma. Fixed an issue that caused the panel to have too much space in it until restarting Plasma if you stop displaying the date on a horizontally-laid-out Digital Clock widget. The older Plasma 6.3.6 fixed video stuttering on variable-refresh-rate screens and patched the Weather Report widget after Environment Canada changed its data format. You can check out the full update on the official KDE Blog.
    • I'm happy with my setup. I have a raid 1 two drive Synology setup that I backup with Time Machine to every so often. What is your setup at home? 
    • Enterprise support (ex. Premier Support) is a bit different cup of coffee. I am not saying it is great, but they have SLAs and I have received solution within hours and even patches within 3 days.
  • Recent Achievements

    • One Year In
      TsunadeMama earned a badge
      One Year In
    • Week One Done
      shaheen earned a badge
      Week One Done
    • Dedicated
      Cole Multipass earned a badge
      Dedicated
    • Week One Done
      Alexander 001 earned a badge
      Week One Done
    • Week One Done
      icecreamconesleeves earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      569
    2. 2
      ATLien_0
      187
    3. 3
      +FloatingFatMan
      184
    4. 4
      Skyfrog
      112
    5. 5
      Som
      108
  • Tell a friend

    Love Neowin? Tell a friend!