bj-kaiser

imagex doesnt care for boot sectors, it just saves the files in the partition. you will have to apply a boot sector with bootsect.exe from the WAIK.

RTFM: (AutoIt's Helpfile) Macro Reference ... @AppDataDir - path to current user's Application Data ... @ProgramFilesDir - path to Program Files folder

did you try to set a fixed speed of 108 Mbps? and BTW: IEEE standard 802.11: 802.11g = 54 Mbps, 802.11b = 11 Mbps. 108 Mbps = non-standard proprietary tricks, channel bonding, etc.

if you got enough RAM, why dont just load the (average of my builds) 100 MB to RAM? (like from CD/UFD) That way you will only have the bootloader and .wim file on the HDD. No single files. Downside is, updating is more or less of a hassle (depending of your view on it). You have to modify the .wim image for any future changes instead of directly manipulating the files. If there is any interest I'll try to look into RAMdisk boot from HDD if not somebody has done it before. edit: Wake-on-LAN + PXE should do it. I.E. your Server wakes up the PCs one by one remotely, booting them into PE from which you start some sort of setup routine. You will need some scripting, but it should be the better way than placing a WPE image + bootloader on existing machines. I have something for the re-installation process built in autoit3 that can deal with unattended installation and .wim/sysprepped images. If there is any interest, I can share it.

what he said!

I'm using DokuWiki as some sort of notepad replacement to keep track of the stuff I'm working on. It's a quick way to do some documentation and you can almost be sure that you can still read it like 10 years in the future (given you have proper backups) since DW stores the entries in simple utf8 text files. Not the undecryptable binary/xml crap MS Office produces. However, if I wanted broad support here, I would need a solution that allows single-sign-on against NDS or at least usage of NDS as authentication backend.

just a quick sidenote, i tried diskpart on a machine (mb: Asus A8V-MX, cpu: AMD Sempron 3000) with 256 MB RAM ... it was no problem to create a primary partion of 10 GB. Maybe you get problems if your RAM-disk is to big, mine is about 100MB. edit: duh, nevermind. I have overseen that the box had not 2x 256 MB but 2x 512.

if BIOS and hardware/mainboard revision are the same, it would be weird. i think i have to try that diskpart thing, just that we dont have to much hardware with less than 512 MB anymore.

2 of the options available: http://www.adobe.com/products/acrobat/ http://www.foxitsoftware.com/pdf/pe_intro.php Another option would be to use MS Office with a pdf-printer driver or OpenOffice.org with its pdf export. So you wouldn't edit the pdf itself, but the source document. One example for a pdf printer driver: http://www.pdfforge.org/products/pdfcreator

This one is probably more of a hardware problem. I have read that even if you have a machine with USB 2.0 ports most of them only support USB 1.1 for booting (BIOS issues). Your newer vista capable hardware seems to be free of that problem.

http://www.autoitscript.com/forum/index.ph...st&p=316159 there is the solution. though i would prefer to use the .dll instead of adding another wrapper around imagex. One trick you could try also would be AutoIts BlockInput() function, it will disable every mouse and keyboard input other than Ctrl-Alt-Del.

Stdoutread and imagex != fun. Since imagex.exe seems to suffer from an error similar to the one found in wimgapi.dll. You will see the output of imagex.exe only after the program ended. I.e. as long as you run it from cmd.exe it looks ok, but if you want to redirect the output be it a file or read into AutoIt, you will not see anything until imagex.exe is done. And thats not what we want. But so far there seems no solution to this behaviour other than let imagex.exe run from a wrapper that redirects the output ... i will see if i can find that link again.

Would you be interested in wimgapi/imagex integration into AutoIt? I already have done some work there. The only thing that doesn't work is setting up a callback function to visualize the progress while the image gets applied, for capture it works gracefully. (this seems to be a bug in the wimgapi.dll, read the thread in the autoit forums) This is my latest include for wimgapi.dll (at the moment) http://www.autoitscript.com/forum/index.ph...st&p=385299 You will also need DllCallback.au3 from here if you want to use a callback function for capturing: http://www.autoitscript.com/forum/index.ph...st&p=384128

create a custom application in a script/compiled language of choice and let it run as shell. That way you have full control over the session. search the docs and the forum for winpeshl.ini

maybe you should give this a try: http://www.sandboxie.com/

rule of thumb: search sourceforge and look what you get there. http://fullsync.sourceforge.net should be interesting.

I prefer AutoIt3 (beat me, was the first scripting language i stumbled upon). It should be easy to get a grasp of it since it's BASIC like and some stuff works similar to PHP. AND: All you need (if you dont use include files) is the 300KB autoit3.exe. I have that running within WinPE 2.0 without much tricks. The next option is VBscript as zorphnog supposed. Has the advantage that it's from Microsoft and shipped with the OS so you won't get asked what weird stuff your autoit3.exe is (or get beaten upon if you have policies that forbid downloading executables ...). One sidenote, I don't know if autoit3 runs on X64. Didn't have to try it yet. In case it doesn't just go with VBscript. btw: they have a Beta version for X64 http://www.autoitscript.com/autoit3/files/beta/autoit/x64/ This is only the interpreter. You will still need the standard package for documentation and customized Scite editor. http://www.autoitscript.com/autoit3/scite/downloads.php

hm, maybe i misread something in the docs. I supposed since Sysprep copies its Sysprep.inf to $winnt$.inf upon execution, it would use the later file for mini-setup. As you found out you seem to still be able to use sysprep.inf after running sysprep. Way to go i suppose.

Hi kaiser, and thank you for your reply I am using the Windows PE which comes with Windows Vista AIK, which can be downloaded from Microsoft's website. I assume that it might be version 2.0? How do I make it work like RIS, so that I can decide the computer's name? This is my biggest issue at the moment. Thank you in advance // Preben I would try to use some scripting language to modify $winnt$.inf (should be in the windows\system32 dir) after applying the image. Thats the place sysprep.inf gets copied to (IIRC, search the docs). Using a script language to modify that file would have the advantage that you dont have to wait for the reboot to be done, instead you can set the new computername directly from your WinPE session. This is all based on having a sysprepped image.

Shouldn't Windows 98 also have the Setup SourcePath Registry Key? Try looking at HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath.

the question is, what WinPE are you using? PE built from XP/2k3 files (1.X) or built from Vista's WAIK/Setup files (2.0). The later one is easy to chainload from pxelinux since it's fairly good documented in the WAIK docs and requires only DHCP, DNS and TFTP services. The first one is a b***h to get booted by PXE from a non-windows server.

what are you trying to achieve? The limit is per session, and that means per connected user (correct me if I'm wrong). So what do you want to do that goes over that limit?

wpeutil /? there should be something about enabling networking. http://www.msfn.org/board/index.php?showto...st&p=605490 and btw: empty ipconfig can also be missing network drivers.

https://addons.mozilla.org/firefox/addon/2553 what I really dont find is a way to disable the "Profile Migration Wizard" aka the bookmark import window. Maybe the CCK does also help there, since you can preset settings in about:config. (but I dont know which one would disable the migration wizard) maybe this helps, not tested however. add the following setting to the default firefox settings within the CCK wizard: profile. allow_automigration : false

why dont you just script the windows you want to automate with AutoIT and use WinWait to wait for the window after the one you'd like to fill manually?