Jump to content











Photo
- - - - -

Need some handholding w/ .Script & drivers.

newbie help .script thinapp win7pe

  • Please log in to reply
3 replies to this topic

#1 notsteve82

notsteve82
  • Members
  • 2 posts
  •  
    United States

Posted 18 October 2011 - 04:35 AM

I’m really new to this so forgive the handholding. I installed win builder its dependencies
and successfully created a boot usb w/ Multi-PE based on Win7, played around with it
on a couple of systems and it is really exciting environment! However certain things I am
having a difficult time conceptualizing.

I would like to load some vendor applications for offline RAID management (for HP & Dell Servers).
I am also going to need to integrate drivers into “Multi PE” and include some offline AV tools.

Question 1: Is there a way to easily integrate drivers into a Multi PE permanently? I see the
“Driver Importer for PE” but cannot determine if it allows you to import drivers into a live system for the current session,
or does it permanently integrate the drivers into the build?

Question 2: Inserting your own applications as scripts really has me stumped. Is there a utility (like Vmware ThinApp)
that will simply “watch” an install and generate the files & registry keys needed to Run in a PE environment? MSI builder comes
to mind with it sitting in the background and recording all the changes an installation makes and dumping it to a portable MSI
installer for redeployment. I tried the help links for script building but they appear to be broken. I’ve even looked opened some
.SCRIPT files in notepad and see how they were written and it still doesn’t really make any sense.

Question 3: What does it mean when a project is discontinued? I looked at Win7 Rescue for AV cleanup
and it looks spot on but I’m leery about this discontinued message. What exactly is discontinued from it?

I appreciate any help the community can provide and thanks for reading.

#2 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 18 October 2011 - 05:46 AM

Question 1: Is there a way to easily integrate drivers into a Multi PE permanently? I see the
“Driver Importer for PE” but cannot determine if it allows you to import drivers into a live system for the current session,
or does it permanently integrate the drivers into the build.

Not sure which script you refer to but if it's using DPInst or DrvLoad, it's the former; if DISM, the latter.

Question 2: Inserting your own applications as scripts really has me stumped. Is there a utility (like Vmware ThinApp)
that will simply “watch” an install and generate the files & registry keys needed to Run in a PE environment?

There are programs like TotalUninstall that do this but I still prefer What Changed and Advanced Registry Tracer. The registry capture needs to be converted to script using reg2Wbs or regCPE.

Question 3: What does it mean when a project is discontinued? I looked at Win7 Rescue for AV cleanup
and it looks spot on but I’m leery about this discontinued message. What exactly is discontinued from it.

Just means it's not actively updated or supported but may still be a nice project.

#3 sbaeder

sbaeder

    Gold Member

  • .script developer
  • 1334 posts
  • Location:usa - massachusettes
  •  
    United States

Posted 18 October 2011 - 04:02 PM

I’m really new to this so forgive the handholding. I installed win builder its dependencies
and successfully created a boot usb w/ Multi-PE based on Win7, played around with it
on a couple of systems and it is really exciting environment! However certain things I am
having a difficult time conceptualizing.

I'm going to guess you mena the MultiPE project...a good choice, and Peter (pscEx) does a good job supporting it...It's goal is to support a lot of different "source" versions to be able to have one project that makes all sorts of different PE environments.

I would like to load some vendor applications for offline RAID management (for HP & Dell Servers).
I am also going to need to integrate drivers into “Multi PE” and include some offline AV tools.

Question 1: Is there a way to easily integrate drivers into a Multi PE permanently? I see the
“Driver Importer for PE” but cannot determine if it allows you to import drivers into a live system for the current session,
or does it permanently integrate the drivers into the build?

As amalux already entered, it all depends on HOW the drivers are integrated. You might want to look more at the Win7PE_SE project, since it has some scripts that do it each of the ways mentioned. BUT, it will require you to look more at the scripting to see what it actually does...Which leads to the next question

Question 2: Inserting your own applications as scripts really has me stumped. Is there a utility (like Vmware ThinApp)
that will simply “watch” an install and generate the files & registry keys needed to Run in a PE environment? MSI builder comes
to mind with it sitting in the background and recording all the changes an installation makes and dumping it to a portable MSI
installer for redeployment. I tried the help links for script building but they appear to be broken. I’ve even looked opened some
.SCRIPT files in notepad and see how they were written and it still doesn’t really make any sense.

OK...Working backwards...first off, you don't need to use notepad, since winbuilder has a built in editor. Are you using the latest winbuilder? If so, then the "help icon" will take you to the web site that now hosts all the docs (or go directly to the "wiki" at http://code.google.c.../wiki/wbwelcome Look at the docs on the tool (in addition to the API and command docs). But building a script takes a lot more work, and I don't know of any tool that will be "push button" for a tool that needs a lot of registry entries.

RANT - ON....
For me, this is just poor program design, since a program should be able to (for the most part) re-create it's environment when executed, and shouldn't need a lot of registry entries, etc. OK, maybe for low level drivers, but too many programs take things to extremes, and then on an un-installation leave all sorts of "crud" behind...
RANT-OFF...

Scripts are all pretty simple, once you get the hang of the language and the way it works...Keep plugging away, and it will "click"...

Question 3: What does it mean when a project is discontinued? I looked at Win7 Rescue for AV cleanup
and it looks spot on but I’m leery about this discontinued message. What exactly is discontinued from it?

I appreciate any help the community can provide and thanks for reading.

Amalux covered this one pretty well too...it just means that the main author has "moved on"...so you can certainly look at it, and learn from it, but (as in this case) it probably won't work on the SP1 of win7...

You're also getting into a lot of more complex PE items (i.e. trying to work with RAID, etc.) so study up on some of these topics on the Microsoft sites related to PE might also help you understand more on how drivers integrate, etc.

And good Luck, and just ask!

#4 notsteve82

notsteve82
  • Members
  • 2 posts
  •  
    United States

Posted 20 October 2011 - 02:51 AM

Thank you very much! I saw the script editor built in Winbuilder, it looks GREAT, better than notepad!

Also I just located DISM tool GUI for injecting drivers permanently here and will give that a try.

I'm going to play around with it in the next few days but this is a great start! Thanks.





Also tagged with one or more of these keywords: newbie help .script thinapp, win7pe

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users