tistou77
Content Type
Profiles
Forums
Events
Posts posted by tistou77
-
-
The question is : removing WHAT component(s) generates Vlite crash ?
just remove "file and printer sharing (server)" generates Vlite crash...
0 -
ok, so Vlite works great with Windows 7 and sp1 integrated but not with windows 7 sp1 MDSN
with the method of monkie53 (replaced wimfltr and wimgapi) the problem is that Vlite closes itself after the removal of components (we just unmount the image with dism but some "adjustments"are not applied)
for example, I disable UAC, but the padlocks are still some folder
and I delete "file and printer sharing (Server) but I still have these options in Windows 7 after installation
how to have Vlite compatible with Windows 7 sp1 MSDN without it closes by itself?
EDIT: I noticed that when it removes components with Vlite it closes by itself, if you add drivers, we made adjustments, there'll have no problems ...
0 -
Dates of install.wim or boot wim are not relevant, is the date of release creation (depends of the creator) , but the rest of files date is 11/20/2010 when SP1 MSDN was released. Setup files, bootmgr and many other files are different (not just by date) between images and I think that vlite have problems with newest SP1 files.
and what needs to be changed then?
for Windows sp1 MSDN works with Vlite
that's what I do not understand
thank you very much
0 -
Indeed, if I integrate SP1 to Windows 7 ISO, Vlite works fine
if I use Windows 7 SP1, there are problems with Vlite
what is the difference between a Windows 7 SP1 and Windows 7 with sp1 integrated
just the SP1 Update in Windows 7 sp1?
and I still do not understand the history to change the date and time ^ ^
named "07/13/2009 kit", the one that have SP1 slipstreamed. Vlite works perfect with that image.
what do I have to rename in 07/13/2009 Kit (with windows 7 sp1 MSDN?)
I watched with a Windows 7 and sp1 integrated
date of install.wim (example) is the January 17, 2011 and no problems with Vlite
I do not know what to Modify
thanks
EDIT:
for the windows folder
creation date: 13 July 2009
modifiaction date: February 23, 2011
same for the winsxs folder
0 -
how to change the date and time of the Windows and Winsxs folder?
when using vLite, we did not have time to make this change?
if you mount the image before using Vlite date is July 13, 2009 and 8:20 p.m.
how can we do?
thanks
EDIT: I compared the dates/times (creation of file and date modified)
after using Vlite modded and true Vlite and that the same (et also Rt7lite)
I don't know what to do
0 -
then, there is always Vlite that closes by itself, with a command dism,i unmounting install.wim and I run Vlite, then I can finish the process,
but some components that I deleted are still present (after installing 7, for example, I disabled UAC, but I Always padlock on some files, I deleted file and printer sharing (Server) but it is always present)
is what it'll have a solution to make it compatible Vlite with 7 sp1?
0 -
ok, you have to start every time, where there is something to be done to make it work
can be used as before or has some options to "avoid"
thanks
0 -
I downloaded and installed the WAIK for Windows 7 (WAIK3)
on C:\Program Files (x86)\vLite\wimfltr, I copied the x86 and x64 wimmount.sys in their respective files, deleted the wimfltr.sys and renamed wimmount.sys in wimfltr.sys
on C:\Program Files (x86)\vLite, I copied the x86 wimgapi.dll of WAIK
I uninstalled/reinstalled wimfltr with InstWimFltr (of Win7PE_SE)
during the process, Vlite closes by itself, while cleaning (after the removal of components)
what did I miss something?
thanks
EDIT: I also tried putting the WimFltr.sys of WAIK (6.1 7600.16385) in C:\Windows\System32\drivers but without success, same error (vLite closes)
I need help!!
0 -
Here is the way I got it to werk, NOW THIS IS NOT FOR EVERYONE SO TRY THIS AT YOUR OWN RISK!!
I replaced in Vlite's root folder wimgapi.dll with win 7's wimgapi.dll from WAIK tools ( WAIK tools folder -> x86 folder\wimgapi.dll )( have to download the iso from MS ) and install WAIK to get these files .
You will need to uninstall the Vista wimfltr that is loaded on your PC ( if you have ran vlite after installing it ) as the files from WAIK 7 are not the same , not sure how to do it manually as I have the InstWimFltr.exe by JFK from a winbuilder project that I use, that will uninstall the wimfltr of Vista's ( yep fixed that winbuilder project too with WAIK 7 Files )
Also a reboot when uninstalling these files wont hurt, after removal of the wimfltr of Vista's just to clear any memory that might be latched onto these files.
From WAIK, I also copied in the x86 and (amd64) wimmount.sys replacing wimfltr.sys by renaming wimmount.sys to wimfltr.sys respectfully in both x86 and x64 folders so yes delete wimfltr.sys in both folders first then copy in the win 7 files .
I didnt change the wimfltr.inf at all, I left it as vlite installed it, I just replaced the wimfltr.sys in Vlite's folder with wimmount.sys from WAIK and renaming it to wimfltr.. easy peasy
what you end up with is Vlite using win 7 dll files, it werkd for me, but I got a error or 2 at first, then they went away, I made 4 builds back to back with the SP1 x64 and everything was fine and the iso installs fine too.
NOTE: even uninstalling Vlite from Add | Remove Programs DOES NOT UNINSTALL the Vista wimfltr!
NOTE 2: After running Vlite on a win 7 moddin win 7 have you ever encountered that DISM fails( Pre SP1 iso files that is )??
NOTE 3: I got a few small errors after doing the above from Vlite, but after a few errors passed all was good hence the TRY IT AT YOUR OWN RISK.
Anyways maybe that is enough for some more knowledgeable person to figure out a better werk around than what I have done.
Vlite does the job I want quicker than RTLite, RTLite is way to slow and seems like it wants to just freeze up the whole time I run it,.. a scalpel over a hammer any day lol , this is my werk around for that
thank you for this feedback
can you put the files/dll (x86/x64) substitution in the attachments (archive)?
I don't understand English very well, if you could make a "tutorial"to indicate which files to replace
thank you very much
0 -
You have at least two viable options. Maxxpsoft's weird chaotic tool and then Bensam56's RT7lite. Both will get the job done. There is no point in vLite at all.
I already rt7lite, but it's not as though some thing Vlite
Security Center is not completely removed
if you disable UAC, there is the padlock on certain folder, and all options are not deleted (Share with, etc...)
0 -
someone could resume work of Nuhi, and make a 7lite?
which could be used later to Windows 8
0 -
-
I would say then that vLite has now become obsolete...
that's what I think too... Vlite was really good
0 -
I use Vlite 1.2 and Windows 7 SP1 (MSDN) and after I get errors (.dll corrupted, modified, etc ...) why?
when I was using it with SP1 integrated windows 7, no problem
thank you
EDIT: see post #105 for manipulation to be done to make Vlite compatible with Windows 7 sp1 MSDN
0 -
Are you creating a answer file?
not understand
Did you remove the cmd tools?
no
Did you delete ANYTHING off of the iso? (Yes I KNOW you removed stuff from the wim with vlite)
see .ini file above, for what I deleted
Also HOW sure are you the source is genuine?
ISO is a genuine Microsoft DVD
thanks
0 -
help please
0 -
it's OK, problème with ISO of Windows 7
0 -
-
Hi
I have a problem with vLite, since yesterday, if I use Vlite, the processors drivers will not install (driver intelppm.sys)
if I install without using vLite, no problems (Updates integrated ISO with DISM)
Why?
thanks
0 -
I integrate the microsoft updates to ISO, and I delete the winsxs, not be a problem later to uninstall updates, what do I do?
first remove winsxs and after incorporating the updates?
Do not delete the file "pending.xml" and change something?
thanks
0 -
someone can help me....
0 -
help
0 -
must remove winsxs with Vlite and delete the file pending.xml?
I'm the opposite, it's serious?
thanks
0 -
Perhaps this
Method 1 : just remove Pending.xml from winsxs dir using imagex.exe [before u delete this file u need to know its like file with some proccess that need to be done after doing update or removing or adding packages mostly not effect the system]or
if u don't ever used imagex or dont have waik install...
Method 2 : Forcely finishing setup by running cmds while the setup
or I misunderstood
0
[SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)
in vLite
Posted
I can already make a list of some .dll and files corrupt and modified
I think Vlite removes components correctly but when cleaning (just after the removal of components) that vLite crash...