Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About arpharazon

arpharazon's Achievements



  1. I tried vLiting W7 7100 today. Removed relatively few things. I have been using nLite quite a bit lately for both XPx64 (main OS) and XPx86 (want to put it on a laptop). W7 installed OK, but wouldn't do it unattended. I entered the user name and it has no dropdown for timezones in vLite. So it asks for a username and the timezone during installation. Also, is there any RunOnce option in vLite? I didn't see any way to run a batch file for addons like I did in nLite. Last_Session.ini Thanks.
  2. I am thinking of trying vLite to slipstream Win7 x64. I have been using nLite on my XPx64 to SS both the XPx64 and x86 and have gotten them both to work well. But, is there any way to get vLite to work (under my XPx64 environment) without this WIM filter? If not, can anyone give me some help how to install this .iso and where? Edit: Never mind, after downloading the .iso, it automatically finds it and runs. Thanks.
  3. A new issue. I set this slipstream up to login as the admin. After a couple boots it gives me the login screen for the admin password, but I type it in , hit enter and it ignores it and the password field goes back to blank. Edit: Though after changing the P/W to the same in User Accounts, it works OK to get back in.
  4. I went with the direct integration of WMP and added IE7 and it's few hotfixes into the hotfix step. Weird thing is, WMP11 runs OK without wanting to be validated, whereas in x64, the direct integration wanted to be validated afterwards and the pre-integration "version" worked fine. I put the WMP11 hotfixes into the RunOnce folder and added them to RUN1_XP-86.BAT which I had left out of the last few installations. The batch file also has net framework and it's SP's, directX and other items. Again, I went with the x86 versions of everything I had in there for the x64 installation. This has worked well. No errors about missing .dll's and everything seems to work and is the correct version. Screen resolution still starts at the minimum (800x600). I may try some device drivers in an HW environment. LAST_SESSION.INI RUN1_XP_86.BAT.txt
  5. Right now doing VMware and it keeps coming up as 800x600 when I have it set to 1024x768 in Unattended. And like you said before, even if I had "normal" drivers included, VMware ignores them. If you remember, I never had any luck with drivers on my X64 SS on HW. But under x64, the resolution was always what I set it as with no drivers. Not a huge deal to set it afterwards, but strange that it doesn't work right in XPx86. I've never gone with the virtual drivers, since it wouldn't be an accurate representation of what the "real" drivers would do in an HW installation, and I used VMware to iron out these other quirks without spending too much time on it.
  6. OK. Ran it without ANY WMP or (apparently) IE integrations, it finished without any errors. It still ignored the resolution settings I set up in unattended, and has WMP9 & IE6. I think I'll try adding WMP11 without it's own hotfixes integrated next.
  7. I am running nLite under my XPx64, the compatibility mode goes up to "Windows XP" with no SP's. Net Framework and it's updates (and some other items) are all under RunOnce and are included in the batch file. I tried to leave this set-up the same way I had under the x64 slipstream, just with x86 versions of the files. I pre slipstream WMP11 with it's hotfixes/updates and integrate it into the root folder for the installation, also the same as I did for the x64. I found that pre-slipstreaming it avoids the need for validating it. Unless there is some problem doing this for x86 and not x64? And yeah, I think there might be an issue with the order of the hotfixes. With my x64 SS, I added the 3 digit numbers Kurt_Aust had on the hotfixes. The #'s didn't carry over into nLite, but I think the #'s kept them in the proper order when nLite did integrate them. I haven't found a hotfix list for x86 that has this type of numbering, so I'm unsure of the correct order. I know with the previous list (x64) that the hotfixes were not always in "KB#" order.
  8. On the original XP Pro disk, framedyn.dl_ is in the I386 folder, wmdrmsdk.dl_ is not on the disk anywhere. They are both in the I386 folder in the root folder for this installation under nLite. SP3 could've put it there. Batch file, with .txt added to allow for upload: RUN1_XP_86.BAT.txt
  9. I had these same errors during my first attempt to slipstream XP Pro (32 Bit) and thought it might be related to mis-ordered hotfixes. Then I downloaded RyanVM's hotfix lists and tried again, resulting in the same problem(s). I had started from scratch this time, even going so far as to uninstall & reinstall nLite, no change. Got this 3 times in a row during the windows installation process and a couple more times during/after the addons installations: And during the DirectX installation: LAST_SESSION.INI
  10. Dammit. I didn't even notice it had pulled up the x64 one. I've got both installations in the nLite folder. Thanks, I'll try it the right way and see what happens.
  11. I got my XPx64 slipstream working great, with a lot of help from johnhc and Kurt_Aust. Now I'm trying to do the same with XP Pro (32 bit). The first try resulted in some errors during installation, relating to missing .dll's and might have had something to do with mis-ordered hotfixes. So I decided to start it again from scratch, this time using hotfix lists from RyanVM forums. Starting from scratch worked out some of the kinks when I was doing the x64 slipstream. Now, it won't integrate either SP3 or SP2 into my XP SP1. I get the following message with either SP ever time now: The worst part (I think) is, that it did this step the very first try, it just had issues during the actual Windows installation. I even tried putting nLite on my laptop (which it was never on) to try this, and got the same result. Anyone seen this issue?
  12. Mainly it's the latest (or almost latest) versions of these apps. Office 2007, PhotoShop CS3, etc. I was thinking it might be an intended thing to prevent "abuse" by installation to multiple computers or something.
  13. Don't know if this is anywhere else, I apologize if it's been covered. Currently my machine has 3 HDD's with one (G:) generally used for testing Win7 or testing slipstreamed installation of XPx64. Otherwise, C: has the main OS and drivers, and D: has most non-driver applications including Office 2007, PhotoShop, Corel apps as well as My Documents. Whenever I have had to reinstall XP, the least of what I need to do is repair the installations of most of the major apps on D:, if not complete reinstallations of them. Most of these apps don't seem capable of automatically updating in the new registry of the reinstalled OS. Is there anything that can be done before I do an OS reinstallation or after to avoid having to repair/reinstall these apps. I've seen it mentioned, regarding slipstreaming, to use the "current" installation, but haven't figured out how to do that, even if it's possible. I had some luck creating it from scratch, with a lot of help. But is there any way to reference the "current" registry during a slipstream creation, so the new OS will know about the apps on that other HDD?
  14. Probably no help, but I have a Photosmart D7260 installed and it works fine under XPx64. I can't remember if I got the printer before or after I switched from XP 32 bit.

  • Create New...