Jump to content

bj-kaiser

Member
  • Posts

    396
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by bj-kaiser

  1. and you still forgot one thing: imagex.exe which is easily scriptable (because it is a commandline program) and 'free'. free as in, you need to download the 1 GB WAIK and have to build a Windows PE image. Or you can use Acronis. I have a TrueImage 10 License, but I didnt really use it. However, IIRC you can create a rescue-cd/dvd with a system image which will be automatically restored (after you answer 1 question "do you really want to do so"). However, I'd recommend to read the helpfile of the demo or other support material or send a mail to acronis to verify this.
  2. Doesn't look so hard to me. The link I posted tells you how to specify a different network bootloader for a specific machine. So unless it checks for a MS signed loader, you can tell it to use "\Boot\pxelinux.0", put the file and pxelinux.cfg folder into \Boot and that should be it.
  3. maybe I had that worded wrong. You will have to use PXELINUX, I see no way to make a WIM image from any linux installation. WDS native mode still uses TFTP (from somewhere the bootloader has to come), so with the link from the previous post, you can set the network bootloader for a defined machine to pxelinux.0. Everything else you have to do is, to find the TFTP-root of the WDS TFTP server, put the pxelinux.0 loader into it and write a boot config file to install the Linux distribution of your choice. You can even use windows shares for the source files, in most distributions I know, although I'm not so sure about Debian. I don't see how this is any more work than writing a working unattended file for windows. It's just that Microsoft for obvious reasons doesnt have a setup wizard built into WDS to allow you setting up a Linux installation system. Imaging a Linux system to a WIM is harder to archive in my opinion. You would have to setup the Ext IFS driver in your Windows PE, even then noone could guarantee you that imagex works with that drive and you would probably lose the ACLs on restoring. So you would have to setup a script inside the Linux installation that restores the ACLs from a file. I'd go with setting up the pxelinux loader in the WDS system.
  4. If you are running WDS in "compatibility mode" or whatever its called when you have had RIS installed prior to WDS there are ways to boot PXELINUX and thus almost anything non-windows. Search the web for it, I know I have seen it, but I dont have a bookmark at hand. And actually for linux installations imaging is quite uncommon. Most of the time you see "unattended" installations(aka." pre-seeding" for Debian). Ubuntu I remember has the oem-mode which is similar to MS sysprep. But you'd still have to find a way to get that image into WDS. You can be almost sure you won't get anywhere with microsoft's tools. edit: well, never mind. I got something for you http://blogs.artinsoft.net/jose_aguilar_bl...05/16/1442.aspx
  5. personally I like the process Vista uses, ie. a sysprepped image is unpacked to the system partition. however, with XP you have some troubles there, mass storage drivers being one of them. I have one pet project at google code, trying to "missuse" the Vista WAIK for XP. Only that I recently hadnt much time to put into it, due to some big relocations at work. I'm wondering if some people shouldnt join forces on something like that. (since my project is more a hack-around by a single person and not really usable right now)
  6. you could try this: in isolinux.cfg: PROMPT 0 TIMEOUT 500 DISPLAY displayfile DEFAULT mymenu LABEL mymenu KERNEL vesamenu/menu.c32 APPEND bootmenu.cfg displayfile: <FF> <FF> <CAN>splash image file<newline> the <>-enclosed values are control characters, read the syslinux documentation for that. You have to convert the image to a special format, LSS16, see the docs for details. now put your existing menu configuration into bootmenu.cfg. and if I'm not totally wrong, that should be it. -- http://syslinux.zytor.com/wiki/index.php/S..._File_Format.3F
  7. replace menu.c32 with vesamenu.c32 and add the MENU BACKGROUND option. DEFAULT vesamenu.c32 PROMPT 0 MENU TITLE openSUSE 10.2 MENU BACKGROUND os102.png
  8. hm, just try enclosing the whole commandline in quotes. It dawns to me that the documentation wasnt really close to reality.
  9. without looking at my winpeshl.ini, maybe this is worth a try? [LaunchApps] cmd.exe, "/c %systemroot%\System32\Startnet.cmd"
  10. In launchapps, the commandline options are separated by a ", " from the executable/command. http://technet2.microsoft.com/WindowsVista...88eb651033.mspx
  11. didnt know Windows XP had boot options for that. well, should have searched the knowledge base, I guess. http://msdn.microsoft.com/en-us/library/ms791480.aspx
  12. net help use "net use Z: //host/share /U:user password"
  13. so you want a remote terminal session or SSH? how about this one: http://www.xk72.com/midpssh and if the free software just doesnt cut it for you, there is always at least one commercial one: http://www.rovemobile.com/products/networkadministration/ssh (dont look at the price tag)
  14. That'd be the one that gave HP the blame intelppm. I had that problem too. and I had my own ideas about it, after I finally found out what was the reason for the reboots. my take on that one: http://code.google.com/p/unixp/source/brow.../workaround.au3
  15. If I remember right, the AutoIt recorder works by scripting mouse movements, ie. it writes the coordinates of your mouse clicks to the script. Now if you change the screen resolution it all goes *kaboom* on you. Best idea, play around with AutoIt, learn the basic functions to control installers (ie. ControlClick, WinWait...) and try other options first. Like installer answer files if such an option is documented by the software vendor or the vendor of the installer system (for MSI for example its called "administrative installation" iirc).
  16. I concur, there are easy ways around the HAL limitation. They are just not supported by MS. In the end unpacking and renaming the right files actually works like a charm for me.(well, I dont have so much systems to test that on, I have like a hand full of different hardware types at work, ranging from ACPI-PIC to ACPI-APIC MP) So what are these unsupported easy ways around the HAL limitations? The unsupported way is to replace the HAL depending files with copies for the right HAL, youll find those files inside driver.cab or SPX.cab. my take on that one: http://code.google.com/p/unixp/source/brow...unk/lib/hal.au3 and since I know that's hardly comprehensibel (even if you know AutoIt, I know my coding "style"), here the simpler version with comments: left filename is source (driver.cab or SPX.cab), right filename is the target filename in SYSTEM32. HAL "ACPIPIC_UP" halacpi.dll -> hal.dll ntkrnlpa.exe ntoskrnl.exe HAL "ACPIAPIC_UP" halaacpi.dll -> hal.dll ntkrnlpa.exe ntoskrnl.exe HAL "ACPIAPIC_MP" halmacpi.dll -> hal.dll ntkrpamp.exe -> ntkrnlpa.exe ntkrnlmp.exe -> ntoskrnl.exe If you need to support other HALs, just have a look at %WINDIR%\Inf\Hal.inf. some helpful links: http://www.911cd.net/forums//index.php?showtopic=19397 http://www.myitforum.com/articles/15/view.asp?id=8997
  17. I concur, there are easy ways around the HAL limitation. They are just not supported by MS. In the end unpacking and renaming the right files actually works like a charm for me.(well, I dont have so much systems to test that on, I have like a hand full of different hardware types at work, ranging from ACPI-PIC to ACPI-APIC MP)
  18. I tend to treat AutoIt as the last option. Most Installer systems for Windows have silent switches or a possibility to define answer files. The problem is that there is not "one way to rule them all".
  19. Geogebra: http://www.geogebra.org/forum/viewtopic.php?f=5&t=2874 Pagedefrag: if the EULA popup disturbs you, look for a registry value that is created after accepting it. just import that to the registry unattended in your installation and you should be set. Auslogic Registry Defrag: uses the InnoSetup installer system, you can create an answer file by running 'setup.exe /saveinf="file.inf"'. The other way around is (obviously) 'setup.exe /loadinf="file.inf"'
  20. imagex.exe and WinPE 2.0. Both available from the freely downloadable Vista WAIK. http://www.microsoft.com/downloads/details...a5-5b50c657de08 one big thing, 1375 MB. imagex.exe is a command-line tool, however, there are already GUI wrappers like GImageX
  21. you know you could just use the search on the autoit forum... http://www.autoitscript.com/forum/index.php?showtopic=5647
  22. well, the trick seems to be that .DEFAULT isnt really connected to "UserProfilesDir\Default User\ntuser.dat". try to "reg load" the default user ntuser.dat and modify the loaded hive. syntax: reg load HKLM\Something Path-to-ntuser.dat dont forget to call "reg unload" after you did the changes. I'll see if I can find a MSKB article on this, for now, you have to trust me.
  23. If one really wanted to have a Chat possibility, I'd be all for freenode. Except if someone sees a catch in their rules. Personally I think MSFN could go with #6 WebMedia. But maybe they dont like microsoft related stuff at freenode. http://freenode.net/policy.shtml#ontopic
  24. the first thing I remember with that option: http://www.winfuture.de/xpisobuilder3_en
  25. I forgot to make a follow-up to this post. Here is how I solved the problem for me: Use a working copy of the base image (thats what copype.cmd is for). Mount the working copy of the image with /mountrw to an empty directory. Make your customizations, /unmount /commit and /export the image after that to get the size down (set /compress as you need). just don't use the /apply method (applying the image to a folder and recapturing it), I found no way to get arround the ACL issues.
×
×
  • Create New...