Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by mikesw

  1. The extraction directory contains alot of subdirectories that are named based on a language code. So for example,

    there is a subdirectory called en-us. In this directory like all the other language subdirectories there are two files.

    They are, spinstall.exe.mui and spwizui.dll.mui. I still can't remove this extraction directory, and when I exclude (using AVG tool) the drive letter I'm integrating on i.e G:, the subdirectory G:\VISTA and G:\VISTA\mount the $AVG in the root for G: and G:\VISTA\mount are not removed, nor can I delete them. For G:\VISTA, there is no $AVG here.

    I was able to integrate the IE8 SP1 into the VISTA install.wim after IE8 was merged in. The reason it wouldn't do it for me is because I made a mistake in the xml filename. IE8 started the xml filename with "Windows6.0...." whereas IE8 SP1 started it with "IE8-Windows6.0....". Although the docs state go to slp.log (this is a binary) the correct one should be slip.log.txt. In this file I saw the following issues.

    a). unable to prestage file "ieuinit.inf" for component x86_microsoft-windows-ie-setup-support-31bf3856ad364e35_8.0.6001.18828_none_a8ac3b48744f86de.

    b ). The payload directory for candidate component x86_microsoft-windows-ie-setup-support_31bf3856ad364e35_8.0.6001.22918_none_a94a0a7ff8d650ab7 does not exist.

    I guess it's safe to ignore these error messages along with 3 servicingstack Object Not found errors when it tried to look in the servicing subdirectory but found them in the wsxs subdirectory.

    As for ownership of the files within install.wim when mounted, what should they be? Could they all be assigned

    to "NT AUTHORITY\SYSTEM" vs. Administrators or the S- ..... number?

  2. I used ccleaner to prevent AVG from starting up in the task bar and this didn't cure the $AVG being in the install.wim file. Thus, I'll try to prevent AVG from scanning this mounted file as you mentioned above.

    If the mount directory is C:\VISTA\mount\.... do I have to exclude VISTA, then VISTA\mount and I wouldn't

    have to do all the directories/subdirectories under the 'mount' point?

    Yes, both SP1 and SP2 were reverse integrated at the same time with the clean tool for each one run on them as

    they were installed before using WAIK to sysprep them. Vlite wasn't used although I've done that with SP1 slipping on an RTM AIO disk without issues.

    That's interesting that the SP's don't update the IE about version number. Moreover, the wininet.dll can be different versions for the same IE release or SP release, since one verson can be for VISTA no SP, different for SP1 and different SP2 too. I noticed this on WinxP which has SP2 vs. SP3 versions of this file.

    I'll lookup the content of the subdirectories in more detail tonight. The extraction directory though contains alot

    of language codes i.e. en-ENU, and all the other various languages, and within that are a few *.mui files.

    More details later. Once I did a complete reinstall of VISTA, I could easily go to this extraction direction that was

    copied from install.wim to the disk and remove it on the HDD, but just not on the mounted install.wim to save me

    a step.

    Another issue, is even though I logged in as administrator on the computer, during integ of the SP's some files on the

    mount and (sub)directories will have the ownership not as Administrators but as "computername\Administrator". Thus ones computer name will be recorded or associated with an install.wim file. So does it matter if the owner is set to

    "NT AUTHORITY\SYSTEM" for all files or Administrator vs. Administrators (the plural form)? I guess if it has to

    be a certain owner type, one could log into their regular user account that has admin priveleges and just do a "run as" command such that during integration of the SP that the "runas" command will stamp it with the runas username name and not ones own personnel account name. So, one should be able to do "run as" Administrator (or plural form) to have

    all files that were modified in the install.wim have the correct ownership.

  3. I have OEM pre-activated Vista Ultimate that I'm trying to integrate SP1 and SP2 through reverse

    integration. I have WAIK 1.1. After install of the OS and SP's, I created the install.wim file. However,

    I noticed two issues when WAIK mounts it.

    a). A approx 20+ character extraction directory was not removed during SP install and thus during reverse integ

    of the VISTA OS, it ended up in the install.wim file. Moreover, since this is treated as a disk when mounted,

    I see $AVG at the root attached to the mount subdirectory whereby AVG antivirus creates this virus vault.

    Will the $AVG be appart of my install.wim file once it is committed and unmounted?

    I tried changing ownership, permissions=full to try and remove the 20+ character extraction directory which is

    in the mount point of the install.wim, but it keeps stating the the disk is full, that something is using it etc.Thus,

    how do I get rid of this directory so that the install.wim is clean and doesn't show this extracted directory name? I

    suppose I could repeat the slipping process and then check and remove extraction directories created on the disk

    before comitting and unmounting the install.wim (about 4 hours to do the whole process over again). Hopefully there

    is a better way now that the install.wim already has it.

    b). I have integrated IE8 into the OEM install DVD with only one error being generated for "x86...servicingstack......".

    It was trying to find this in the "Servicing" subdirectory too although it found it in the 'wsxs" subdirectory. IE8 full install

    seems to show up when the Vista OS is completely reinstalled. However, I also tried to slip in the Oct 2009

    service pack for IE8, but this didn't seem to get slipped into the OS since when I reinstalled the Vista OS and went

    to About IE8, it doesn't show the new version number associated with the IE8, nor does it show up under

    installed software. How to get it to slip IE8 SP's since MSofts site says this will integrate the same way on VISTA

    although the last resort is to install Vista and do the reverse integration to capture the installed IE8 SP.

  4. the point is that the component which is required for installing updates, servicepacks and changing features has a limitation which doesn't allow you the slipstream ServicePacks. I've used vLite to integrate the Sp1 into a RTM DVd and next Win Integrator to sliptream Sp2 into the image and this damages the Image. When you install the slipstreamed Image it will fail reboot after the OOBE phase and will fail to boot after this reboot. That's why MS disabled sliptreaming of servicepacks in NT6.x (Vista, Win7)

    What is the name of the component that has the limitation? Perhaps there is a free open source one that

    overcomes this limitation.


  5. A neighbor of mine installed Vista Ultimate with SP2 on an old Sony Vaio desktop that has the intel I845G chipset &

    1GIG memory. However, the I8xx chipsets required the Intel application accelerator to handle large drives past the 137gig limit

    since it provided 48-bit LBA disk support along with speeding up bootups etc.

    The problem is, is that Intel doesn't provide an IAA that is VISTA compatible. Thus, does VISTA include as

    part of the OS, support similar to IAA to handle large disks and these old I8xx chipsets? If not, is there

    anything that can be done to prevent large disk drive access problems?

  6. I guess people know that Vista SP2 RTM 6002.18005 is ready for download. However, some may not know

    that there is a vista cleanup tool to remove sp1 obsolete files and also can be used to cleanup slip streamed



    See under setup and deployment improvements section.

    SP2 also includes a Service Pack Clean-up tool (Compcln.exe) which helps recover the hard disk space by permanently deleting previous versions of files (RTM and SP1) that are being serviced by SP2. The Service Pack Clean up tool can also be run offline while creating slipstream images to reduce the size of the image.


  7. I want to make a VISTA OS DVD ISO which already has the 6 or more various VISTA OS versions on it.

    However, Vlite 1.2 requires one to select the directory that contains the VISTA OS and when selected,

    it will display the 6 or so VISTA OS types i.e. home thru ultimate. The problem is, which one to select so that

    I can make a VISTA DVD iso and yet I want the ISO to have all of these OS' too? Can I select anyone

    of them, and when I make the ISO the rest will be there too?

  8. I split a 4.1 gig VISTA SP1 distro into the default 700 mb size specified by vlite v1.2. It said the count would be 10

    but only 8 files were created. Moreover, the first file is a little bit greater than 700 mb (I guess due to the

    powers of 2). However, the remaining 7 iso files created were only one-half of the 700 mb filesize (345 mb) which

    contained one swm file of this size each.

    Why isn't the count vlite states matching the number of files? Moreover, when I specified 700 mb, why are 345 MB files

    being created which requires more CD's instead of just 3-4 disks?

    I used ISOBUSTER v2.5 to view each of these ISO's. I'm wondering why the iso filesystem contains anything

    other than the boot file, and the 2nd filesystem is joilet instead of UDF? This doesn't matter if I look at the single DVD

    that contains the patched OS with SP1 or each of the split CD versions. I thought ISO and Joilet had a limitation

    of 2 Gigs, thus requiring the UDF format. I see each of the filesystems that Vlite creates can record an install.wim

    file greater than the 2 GIG limit.

    Is there a place that I can change the commandline options to the make iso program vlite uses and is the program

    cdimage or oscdimg.exe since the later file can be gotten from WAIK SP1 when it is installed. I thought oscdimg.exe

    has an upper limit of 4 gigs, although Ultraiso says it can create file sizes as big as 2 Terabytes.


  9. I was looking at a friends VISTA OS install disk and noticed in the 'sources' subdirectory

    that it contained,



    Does windows VISTA already come with these two files which are part of WAIK in the

    sources directory? If so, I guess it would be best to update them from the WAIK SP1

    service pack to get newer versions put on the VISTA Vlite'd disk which was upgraded

    to SP1.

  10. Does anybody know the steps to create a bootable XP windows install disk from a DVD but put on multiple CD's?

    Thus, I'd install the first bootable install disk and it will ask me for the 2nd and so on to install XP.

    I see that VISTA can do this.

    If it's hard, can the Windows XP install disk be rearranged to look like Vista's and then create an install.wim file for XP

    so that one can use the WAIK tools on this to create the spanned disks.

    Same question of for w2k too since it is similar to XP's layout.

  11. Since Windows 2K is not supported by MSoft anymore and they won't provide the latest version of KB955839_enu either unless one

    pays $4k per year for extended support, I'm wondering if this windows 2K update list site can provide for download the register fixes

    so that one can update w2K for the latest time zones.

    See this weblink


    a). Thus to get this registry fix for windows 2K (sp4) one downloads and installs

    KB955839_enu.exe (for x32) on a friends PC that has windows XP (sp1,sp2,sp3)

    b ). Then go to this registry key in windows xp and export the timezone database to TZDatabase_KB955839_enu.reg

    and that the name of the exported registry entry corresponds to the current KB article that updates the MSoft OS' with

    timezone fixes. Note: if timezone updates occur in the future, then a new KB # would be specified to identify which

    time zone fix it is. For other world languages, something similar for 'enu' can be done. Perhaps others can specify those

    steps. :)

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones

    c). Then one edits this file in notepad to add to the beginning of the file, the following and then resaves the registry file:

    Windows Registry Editor Version 5.00

    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones]

    d). Although the second subkey specifies saving the current timezone info one has set, it isn't important since during

    Windows 2K install, the user will be prompted for the timezone selection or if unattended settings have already been set,

    the OS will be configured with the proper settings with the above TimeZone database update. The only question is that

    during the update of Win 2K during the install, the unattended timezone setup may occur before the Timezone database

    had a chance to load and update the registry (I think). I'm not sure right now if the unattended setup will be properly

    setup due to the Timezone database update being done later. (others may correct me here).

    The second location for time zone information is the following registry subkey:


    e). Copy the modified registry file in step ( C ) above and put it in the directory of the Windows 2K install disk that is

    used for unattended setups. Some of the commands to update the registry during install are below.

    regedit /s TZDatabase_KB955839_enu.reg


    reg IMPORT TZDatabase_KB955839_enu.reg

    f). I wonder if this MSFN Win2K discussion area can provide a download link to a modified Timezone registry file following the steps above

    and list it with the rest of the fixes so that one doesn't have to pay $4k to MSoft and because not everyone has a friend with Windows XP

    or VISTA or Win 7 etc to be able to get this time zone fix.

    g). Others, can provide the steps for x64 bit or the fixes for win 2k3 server x32/x64


  12. Hmmmm (quick check)... I see what the OP means. To construct a Bootable DVD (not a pre-made image) there doesn't seem to be an option (snapshots attached). First Nero option only allows for ISO; leaves only way by pre-making the ISO by some other means before "burning" via Nero.

    Your image posts for Nero is what I see. I.E. DVD-ROM(boot) and CD-ROM(boot) for ISO only and not UDF. Once you select one of these

    the corresponding tab will only show ISO for these formats and not UDF.

    Moreover, the 2nd image shows the iso and udf icons which give one the ability to boot the DVD to install VISTA. If one tries to

    create a DVD bootable ISO with NERO and copy the whole VISTA dirctory structure off the HDD to the NERO program, it will detect

    the install.wim being greater than 2 gigs and complain that UDF should be used and copy everything over but files greater than 2 gigs.

    But if one tries to do a this in NERO as UDF, Nero doesn't allow you to make the UDF bootable. Nor does it allow one to create

    a DVD with both ISO and UDF on the same DVD - which is needed.

    I guess NERO isn't as advanced as I thought it was.... but UltraISO seems to have been doing this since 2006.

    45, UltraISO 8.0 PE(Premium Edition) (April 13, 2006)

    +) Supports UDF DVD images, can add/extract files above 4GB large (up to 200GB)

    +) Can create bootable UDF images (such as bootable DVD of Windows Vista)

    +) Can mount ISO image to virtual CD/DVD drives of Daemon-Tools 4.x and Alcohol 120%


    +) Can change disc label of ISO images with UDF volume

    The FAQ says it supports up to 2TB instead of 200GB. This is the limit of the MBR record for NTFS support.

  13. I have a VISTA OS install disk, but it can't boot from the CD/DVD drive upon power on although once the

    OS such as XP is booted and logged into, one can install the VISTA disk and begin installation.

    The reason it isn't bootable is because the install.wim file on it is greater than 2 gigs and requires the UDF format.

    But to make it bootable with a boot.img file it requires the ISO format. As far as I know UDF CD/DVDs can't be

    made bootable.

    The solution to the above problem is to use MSofts oscdimg.exe file which will take the VISTA install files and the

    etfs.com file and create a boot section as ISO and a data install section with the OS files as UDF.

    How can one do this with NERO 8/9? At present it is one or the other. The manuals for NERO ROM don't explain

    this either. Google says there is a an ISO/UDF (bridge), but I don't think this is used to put both an ISO and

    UDF filesystem on the same CD/DVD. ISOBuster will show both filesystems on the DVD correctly. There is also

    the capability to do ISO/HFS too, but NERO doesn't allow one to select HFS either.

    Are there any free programs that can do all this out there to make the job of creating combinations of

    filesystems on the same CD/DVD?

    Does the UDF standard have provisions to make it bootable? If not, then this is probably why CD/DVD writing

    software hasn't implemented it yet....

  14. The FAQ sticky about copying wimgapi.dll may need updating. It says vlite detects

    x64 ; however, there is AMD64 and IA64. Does it detect the wimgapi.dll for each one that are

    in different WAIK directories and copies the correct one? The FAQ may need to clarify this.

    For the x86, it is correct that one has to manually copy the file over.

    One other possible issue with Vlite is that if one installs WAIK manually, the first question

    asked of the user is the directory to store the files in. Of course, it has a default directory

    which vlite probably looks at. But what if the admin/user installs WAIK in a different directory.

    I don't think Vlite will know unless it searches the whole disk, or when one selects the install

    button, that a directory with browse button is shown that allows one to enter the new WAIK

    directory that one installed it to so that Vlite knows where to look and not have to search the

    disk(s). Presently, vlite doesn't provide this directory box so that one can enter the new

    install directory for vlite and remember this path.

  15. MSoft says that WAIK 1.0 and WAIK 1.1 (which is SP1) can't coexist on the same computer.

    Is it possible to install WAIK 1.0 in a directory that I specify vs. using the default and then install WAIk 1.1 in another directory?

    Thus, during the install of WAIK 1.1 it doesn't test the default directory which normally WAIK 1.0 would be in thus getting the

    install complaint of coexisting, but since WAIK 1.0 is in a different directory now, WAIK 1.1 I'd think shouldn't complain.

    Although WAIK 1.1 (SP1) is supposed to be able to install and run on a VISTA SP1 machine, will WAIK 1.0 install on a VISTA SP1 machine

    and work? If WAIK 1.1 is installed on a VISTA SP1 machine, will I be able to use Vlite to modify VISTA (pre-SP1) OS' and modify them or

    only VISTA SP1 and newer SP's?

  16. REGEDT32, not REGEDIT32. It should be there... (?AFAICR)

    Permissions in the Registry.

    I think this is the procedure (roughly) -

    Right-click "section" on left, change permission to allow you (ADMIN sign-on only, otherwise won't work), delete key/value, then change permissions back to original. Can't remember exact details... also you may have to be in Safe Mode and maybe have to have Restore disabled temporarily. May (?) be the way to use CCleaner (Safe/NoRestore/Admin)...

    ? Are you signed on as Admin when you use CCleaner? Also, this is an ActiveX reference you see?

    FWIW, I have a reference to Flash9b.ocx (now using flash9h) but CCleaner doesn't seem to "see" it (???).

    Thanks I'll check out regedt32 tonight.

    CCleaner registry scan/clean won't see your Flash9b.ocx if the entry has no problems. In my case,

    I upgraded to Flash 10 and during the install it deletes the flash9d.ocx file and if it can't properly clean/remove

    the key from the registry file, then the key still references the directory where the file is supposed to reside and since

    it isn't there anymore (deleted) it flags it as a registry problem which ccleaner sees.

  17. In the past I had flash 9 installed. However, I have flash 10 installed now.

    C:\WINNT\system32\Macromed .... doesn't show Falsh9d.ocx since it was deleted a long time ago.

    However, ccleaner shows the HKLM registry reference to this directory file as an issue. When I use regedit

    (W2k doesn't have regedit32 as far as I know) I can find this key and when I delete it, it says

    access denied. I searched all the files on the C drive partition and searched within the files themselves

    for a reference to Flash9d.ocx to see who may be regenerating or preventing its deletion. There is no

    references to it except a install.log file from long ago. Note: I am the administrator.

    How can I delete this registry entry. regedit doesn't permit changing permissions if this is the issue on the key.

    Using "reg delete "HKLM......." /v does delete it but it reappears immediately


  18. I have win2k Sp4 with all the patches. I had in the past installed MDAC 2.53 KB927779 ENU without problem.

    Recently, I was trying to install "SQLEXPR32_SP3.EXE" (the express version) to upgrade the system and it

    complained about not having MDAC v2.81. I thus installed MDAC V2.81 without problem. I ran belarc and

    also MBSA v2.1 and it complained that I didn't have KB927779 installed. Thus I tried to install

    MDAC v2.81 KB927779 ENU and during the install it said it had a version problem and wouldn't go any further.

    Belarc showed the mdac 2.53 KB927779 as an unlock symbol.

    Is there any way to get the install of MDAC v2.81 KB927779 to work. I believe MDAC service packs can't be

    uninstalled. I tried to run spuinst for the MDAC 253 KB927779 that is in WINT too and it complained about the

    version number also.

  19. I see it was already discussed on msfn. :wacko:

    I'm wondering if I can't find a defrag tool that will move my files to the beginning of the disk so that I can

    shrink the partition, will imaging the partition, then reformating it, then shrinking it down followed by

    writing the image back to the formated partiion work? I presume the disk imaging tool is capable

    of moving the files around to fit within the smaller partition size and not complain that the partition is to

    small because some files are at the outer partiton boundary.

  20. Here's info I stumbled across which I didn't know about. It appears that the defrag tool MSoft

    supplies is a limited function version of Diskeeper software which they licensed from them.



    some other interesting info,


    I wonder about Vista and Win 7 defraggers as to who wrote these?

    Msofts pagefile defragger v2.32


    The reason I'm looking into this is because on my VISTA system the OS partition is 500 gigs, but it could

    be reduced to 100gigs. However, I can't use the disk manager to shrink the partition down since some MFT

    files and others are at the 500 Gig boundary of the partition although there is plenty of free space in the

    beginning or middle of the partition. As a result, the disk manager says that I can't shrink anymore because

    it's too dumb as to how to move these files to other areas of the disk. Thus freeing up the outer boundary

    of the partition so that some of this space can be removed.

    I thought the defraggers would move them to the beginning of the disk to optimize not only the filesystem

    but the usage of the partition space instead of spreading all the files all over creation (that is the partition).

    So how can I get around this so that I can shrink the partition down?

  21. no, items that are manually slipped generally do not appear.

    When you say appear, do you mean the dotnet names don't appear in the ADD/Remove

    list and/or the windows component list?

    Does this apply if I use the wmp11 slipstreamer for direct integration vs. the runonce method

    that is wmp11 appears in the add/remove and/or components list vs. no name appearing?

  22. /? will give you all options

    ********.exe /integrate:%path to source%

    you want to aim the path at the folder that contains the i386, not the i386 itself.

    If I do the direct integration route will the dotnet and wmp11 appear under

    Add/Remove Programs in the "Add/Remove Windows Components" list like it

    does originally? Will this allow me to select to install them anytime once the OS is installed

    or remove them vs. having to select Remove from the add/remove programs list.

    I'd prefer if dotnet and wmp11 appear under the add/remove windows components list after

    using Nlite.

  • Create New...