Rasengan

Member
  • Content count

    36
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rasengan

  1. Show us your image if kewl for forum viewing This is the first image I tried with, gonna upload a video of Setup using that image tomorrow to Youtube. Got the FirstUXRes.wim problem fixed, just had to unset read-only flag on FirstUXBackground.bmp before copying a new one over (via the script) EDIT: Video here (http://www.youtube.com/watch?v=RBC-lZeM1AE). Sorry about the funky video size, blame VMware
  2. Have to change the 1 background in the FirstUXRes.wim with my image and it looks real good cause the black background fits real nicely with the new animated logo you see below the 'Setup is preparing..' you see on a setup. You only see this on an actual setup I'll look at your file Ah, well, I was using a light-ish image, so maybe that might have something to do with it. I'm gonna tinker at it, and hopefully get the FirstUXRes image sorted. Also, trying to upload a video (sped-up) to Youtube showing the whole setup with a customized background Never mind, I got that problem fixed, had to tell the script to unset the read-only flag on FirstUXBackground.bmp, changed it, then re-set the flag. Here's an updated script. Pre-edit your files, dump them in the folder and run it. Point it to your WAIK, your DVD source (extracted) and your install.wim image number, and it will do the rest Modify Windows 7 Setup Imagery.7z
  3. Have to change the 1 background in the FirstUXRes.wim with my image and it looks real good cause the black background fits real nicely with the new animated logo you see below the 'Setup is preparing..' you see on a setup. You only see this on an actual setup I'll look at your file Ah, well, I was using a light-ish image, so maybe that might have something to do with it. I'm gonna tinker at it, and hopefully get the FirstUXRes image sorted. Also, trying to upload a video (sped-up) to Youtube showing the whole setup with a customized background
  4. I hope you don't mind, but I re-wrote your script to mount an image modify it automatically, then unmount it, thus saving myself some time. The script is attached, for anyone else who might want to use it. PS> I left our the FirstUXRes.wim, as even after editing it, it seemed to ignore my image, so meh lol PPS> If anyone knows of a utility(or utilities) that can take an image, make multiple copies of it in different resolutions, and then inject those into a dll, I would be happy to hook them up to my script to fully automate the process (basically, you place an image in the folder the *.cmd is in, and run it, and Bob's your Uncle) Modify Windows 7 Setup Imagery.7z
  5. What I actually want to do is have the system set Partition 2 active. Here's the deal: I have an ASUS EEE PC 1201N, with the following partitions: Partition 1: 16MB Partition, ID=EF (Used for Boot Booster) Partition 2: 100MB Partition, ID=07 (System Reserved) Partition 3: 228GB Partition, ID=07 (Windows HD) Partition 4: 4GB Partition, ID=1B (Hidden) The 1201N has a BIOS hotkey (F9) that boots Partition 4. I modified that to contain a copy of the Windows 7 DVD (just Home Premium) and made it Unattended (had to put AutoUnattend.xml into boot.wim:2 for it to be read tho). The problem arises that when you press F9, it sets Partition 4 active (that's all the F9 button does, searches for a 1B partition and activates it). That makes a little boo-boo in setup, as it installs the bootloader to Partition 4, which makes it a little less hidden. So, my preferred setup would be to have the system boot from Partition 4, set Partition 2 active, then show the partition selection dialog (only so I can choose to format other partitions as needed) then continue. I already have an AutoUnattend to do everything except for the Diskpart, and I can post my exist xml if you would be able to provide exact changes, and maybe a sample "LiteTouch.wsf" (keep in mind, that due to the partition being hidden until Setup starts, I have to place AutoUnnattend.xml and any other files into boot.wim:2
  6. Bascially, I have Windows 7 unattended (except for partition screen) from a hidden fat32 partition on my disk. I would like to modify it slightly to call diskpart to set partition 2 active, then continue with the unattended setup as normal. Anyone able to tell me quickly how I would do that?
  7. Yes, I know that, but when running from a 1b hidden FAT32 partition, it doesn't pick it up, I'm assuming that's because the partition is hidden. I fixed it by adding the Autounnattend.xml to boot.wim:2, so that setup would read it as soon as it got mounted as a psuedo-NTFS volume, so I'm happy that that works
  8. I got it working in the end, turns out I had to drop a copy of Autounattend.xml into boot.wim image #2, and it works now, along with my custom backgrounds et al
  9. Hi all. I have an ASUS EEE PC 1201N, which came pre-installed with Windows 7. I've reinstalled it to purge the unnecessary junk they bundled with it, but I left my recovery partition intact. I discovered that it's just a hidden FAT32 partition (ID=1B) which contains the Windows 7 RE set to boot ASUS's restore tool. After changing the partition ID to 0B, I replaced all the files on the partition, with a copy of Windows 7 Home Premium that I tweaked using 7 Customizer. The install boots just fine via the F9 BIOS key, even when the ID is set back to 1B, but, it seems to ignore the Autounnattend.xml file, anyone got any ideas? I've looked around, and tried placing the Autounnattend.xml inside boot.wim in the root, and in the sources folder, with no luck. Also, I would like to customise the setup background from booting to the recovery partition, until setup is complete. I've followed a few threads, including using res hacker to edit imageres.dll and spwizimg.dll, but still no joy with that either
  10. Ok, I can't find that line in my setup.cmd (here: http://pastebin.com/f655e9161). The best I can guess is to change the two lines I've highlighted to the following: SET TAGFILE=\OEM set srcpath=\??\%CDDRIVE%%TAGFILE%\ Would that work, or do I have it wrong?
  11. Yep, search & replace %CDDRIVE%\WINSETUP\XPpSP2\OEM to %CDDRIVE%\OEM.The bolded part may vary depending on your source and if multiple similar sources were added. Ok, will try that, thanks
  12. Maybe you could do this, user runs winsetupfromusb, and is adding a second, third xp source, etc. If DriverPacks are found, offer to move them to root for common use, or leave alone for seperate use (in case of different packs). Cause I would also like a common pack in root, since I'm using the same files. So, what changes would I have to make to achieve that, just move OEM to root, and edit i386/setup.cmd to point there?
  13. Hmm, since any system I will be installing on will have 1GB of RAM, and the XP source fiels were stripped down to about 400MB each, would it be more feasible to just map the entire ISO to memory instead, and possibly modifyit slightly to look for the OEM folder for BTS's driverpacks off the USB instead?
  14. Sorry, didn't see that, will try it now Ok, so tried that. No more biosinfo.inf error, it started loading, got to detecting disks for the partition menu, then poof, STOP 0xED again. Below are my current, semi-working menu.lst and txtsetup.sif (from XP Home Retail) menu.lst title Install XP Home Retail find --set-root /windefault map --mem /WIN_SETUP/XP_Home_SP3.ISO (0xff) map --hook root (0xff) chainloader /I386/SETUPLDR.RTL title Continue XP setup / Boot first internal hard disk map (hd0) (hd1) map (hd1) (hd0) map --hook rootnoverify (hd0) chainloader (hd0)+1 txtsetup.sif [SetupData] SetupSourcePath ="\WIN_SETUP\XP_Home_SP3\" ***snip*** SetupSourceDevice=\ArcName\multi(0)disk(0)rdisk(0)partition(1) BootPath="\WIN_SETUP\XP_Home_SP3\I386\" BootDevice="multi(0)disk(0)rdisk(0)partition(1)" I'm going to try setting SetupSourceDevice to 2, as at boot time, and in grub4dos, the partition is seen as #1, but in the partition screen when booted from my pen drive instead), it's partition 2 EDIT: Doesn't seem to matter if SetupSourceDevice is 1 or 2, both produce a STOP 0x000000ED error at the partition screen, but I can confirm that BootDevice has to be rdisk(0)partition(1) to work
  15. Sorry, didn't see that, will try it now