Madhits45
Content Type
Profiles
Forums
Events
Posts posted by Madhits45
-
-
I have been trying to understand this also. I have removed from my x86 win7 sp1 source with rt7lite and vlite and gotten the image down quite small but not where i wanted it. There is still more that can be removed and youl find directories within the windows folder of your mounted wim that are massive (winsxs & assembly are 2).
There are guides on here of manually deleting files from a mounted wim but the problems are that you can not delete the files without file permission errors because they are protected. Now install_wim_tweak allows you to remove those files without the permission errors but you still have another problem. The problem youl face is durring install. The files you remove are requested by the installer and if there missing you get an error and the install will fail.
I am still trying to understand if there is a central install listing of all files like there was in XP or if its all controlled by the hives in the install.wim. If its controlled by the hives how come install_wim_tweak does not work when you remove files and commit the changes? I recently removed a bunch of files from assembly after loading install_wim_tweak and my install failed. What did I do wrong?
0 -
did u create from the deployment new wim or did u append to same wim ?
its might be also from rtlite config might cause problem with vlite
u could use whereisit application to remove stuff but its hard
IT was a brand new wim saved to a different directory. I cant find whereisit. Can you give me a link to it?
I will try to do the rtlite part againa and see if it works ok with vlite.
Thanks
0 -
aviv00.. I have been trying to get vlite to run with my wim x86 win7 sp1 which has been rebuilt after running rt 7 lite (method 5). I used the apply capture trick with gimagex. This still leads to a problem when using your sp1_2 ini file. Vlite crashes with no error just goes away. I have tried this vlite step on winxp, win7 sp0 and a win7 x64 and its always the same except on the x64 where it says vlite has stopped working and then it asks would you like to close it. I even went back to tried vlite 1.1.6 and its the same. I also tried to remove remove the winsxs from the components removal and no luck either. Is there any way I can do this without vlite? Or do you know why vlite is not letting me progress? It could be because I have a number of updates applied to my win7 sp1. They are security updates but thats all I can think of. Maybe vlite cant handle those.
Any thoughts or suggestions you can offer me? Also have you heard of w7t.exe its a nice gui and allows you to remove winsxs but not anymore then rt 7 lite as far as componts.
Thanks
0 -
I keep having a problem with vlite with windows 7 sp1 and running from host Win7 Sp0. It instantly crashes in the removing componets part. I am still testing to see if some combanation will make this crash stop. I have tried the apply capture and it still crashes. Hope to find an answer but if anyone has some suggestions to that I would be glad to hear.
0 -
Hi all. Just read about 25 pages here, been out of the scene a while.
What I am trying to understand is I have a list of packages I want to remove for a language in windows 7 ultimate x86. The list is complete and when I input it into DISM I get errors after about the second package. I think this has to do with the packages/registery being locked. Whatever this install_win_tweak.exe does I think I need it or whatever tool is evolutionaryly better. I tried it and nullify which did not work same DISM errors. So either I'm doing something wrong or there is an evolutionary better way I have yet to find. Also the link for install_win_tweak.exe is broken here. I got a copy from another site but not sure if its working.
The error I get in DISM is the specified image is no longer serviceable 800f0830
I am trying to remove the following packages:
/PackageName:Microsoft-Media-Foundation-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Branding-Ultimate-Client-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Client-Refresh-LanguagePack-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Client-Wired-Network-Drivers-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-ClipsInTheLibrary-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-CodecPack-Basic-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Disk-Diagnosis-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Gadget-Platform-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-GPUPipeline-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-GroupPolicy-ClientExtensions-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-ICM-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-MediaPlayback-OC-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-PeerToPeer-Full-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-PhotoPremiumPackage~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Printing-Foundation-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-RemoteAssistance-Package-Client~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-SearchEngine-Client-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-SecureStartup-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-ShareMedia-ControlPanel-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-Shell-HomeGroup-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-SnippingTool-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-TerminalServices-CommandLineTools-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-TerminalServices-MiscRedirection-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-TerminalServices-Publishing-WMIProvider-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-TerminalServices-UsbRedirector-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-TerminalServices-WMIProvider-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
/PackageName:Microsoft-Windows-WMPNetworkSharingService-Package~31bf3856ad364e35~x86~es-ES~6.1.7601.17514
Why do I get this error and what tool will help. Believe me I have searched high and low for an answer on this and I keep finding new tools but nothing that actually does what the good old Dism command line tool can do. Ive tried them all and removing this language either fails or never starts. I believe this has to do with the servicable error that I see when I do this manually that I dont see when using jim jim dism tool or RT seven lite etc.
I hope someone can shed some light or point me in the right direction. Been looking at this same problem for over a week now. I hate posting as usually can find stuff but no such luck with this.
0 -
Thank you, all! This posting is immensely gratifying.
>rob.lee
>I found the results less useful than the old style folder search (which I was more than happy to return to).
Now that's an interesting aside. I also removed Windows Search due to the immense gobs of overhead and the lack of granular control over what got indexed. But I didn't see a means for reinstating the old style folder search, so I ended up installing Xobni instead.
How do I enable the old folder search?
That was sufficient for me too. I'd really like to eliminate these indexers that draw my resources away from *my* active tasks and work so as to enable the potential for some future activity that I may or may not actually need. They steal the "personal" from my PC, thinking that they obviously know what I need to have to enable my work activity better than I do. :-)
Thanks!
Mark
Mark,
Like yourself I have always liked the simple search in old XP. Before MS got index happy. Anyway in Win7 I have removed search but the framework of it is still there. It works in explorer and functions like XP's search did almost. I dont really care about it as long as I can do date and file size searches. I use everything search for the rest as its insanely fast. Anyway outlook 2007 breaks the explorer bar search and completely removes it from the UI. It took me a while to track down what part of Office 2k7 was doing it. I should have known it would be outlook. If you keep outlook the search stays.. If you remove outlook the search goes.
Anyway I hate outlook and dont use it. I will keep it for now till I find out a way to re-enable the search in explorer without having outlook installed. It must register a DLL or make a reg entry or something to keep to remove the search. I just dont know what it is. There is no longer outlook express so I'm not sure why this happens.
If anyone has a clue. Let me know.
0 -
**amenx** if you had read that topic its only half the answer. Ramesh in his thread only figured out how to make auto arrange show in the context menu. Have you tried to uncheck it and then close the window and go back to that folder in icon view? Or restart? (not sure about details view)
If you do with his reg applied youl notice that the **** thing just comes right back. That is what got me soo annoyed and why I spend 3 days trying to figure out what values do what and which one could actually turn it off globally.
Not so. When you uncheck autoarrange, it holds that setting when you close the window and even when you restart the PC. I think most people reported the same as well. What it fails to do is make the setting global. You have to uncheck autoarrange for each **** folder you open except the ones you've already unchecked, those remain unchecked. That was my only gripe. Now some even reported @ social.answers.microsoft.com that it worked for them globally, but for most it hasnt. So it seems its not consistent. As someone else mentioned, it may help if you put it into a reg file to get it into wider circulation. I think its not much use just discussing one persons experiences with it which may not hold for others.
* d.amn is a censored word?
Amnex no worries. I could not get it to stay with the other reg so thats why I went looking for a better solution. I think I was the first to figure out what FFLags value causes it to be unchecked & then to apply that to the folder template globally. I've gone a step further now & have foldertypes set with this reg and streams set also but foldertypes only picks up some of the values as there all in streams. Either way I got those set incase I ever hit the folder options reset all folders it will not turn back on. I'll be glad to share that also if anyone cares but as long as u dont reset all folders this reg/settings will stay put.
0 -
It is a neat trick, but you weren't the first to find it.
However, credit where credit is due I've edited my post to point to this thread to make it more discoverable.
Ok not to get really picky. But the topic you pointed to cluberti is for winXP. I tried every single one of the old reg fixes from XP, and Vista before I found this one. Most of the entries are either very different or use new values. MS changed the entries so this feature could not be turned off like it could in the older versions.
**amenx** if you had read that topic its only half the answer. Ramesh in his thread only figured out how to make auto arrange show in the context menu. Have you tried to uncheck it and then close the window and go back to that folder in icon view? Or restart? (not sure about details view)
If you do with his reg applied youl notice that the **** thing just comes right back. That is what got me soo annoyed and why I spend 3 days trying to figure out what values do what and which one could actually turn it off globally. If you look at the comments I tried to ask him for help at one point before I figured it out myself. I also posted my answer on his blog also. I explained what the other values are and what they do and which one I believe controls the Auto Arrange feature. The only ones I dont know are posted below and now in this tread. The only person that I believe can answer these remaining questions is Keith Miller from MS. From his posts at other forums I was able to piece together this solution.
0 -
This is why MSFN has gone down hill. I cant believe no one cares here to even make a comment. This is one of the most annoying features in windows 7 and has more complaints then any other bar none. I have figured out how to bring auto arrange back and no one cares?
WOW
0 -
I've found a solution to MS taking Auto Arrange & Align to grid out of windows 7. I'm coming right from XP so for those of you who knew some of this from vista bare with me.
It should be noted that if any feature disappears from a version of windows and it was in the last version you can bet Microsoft just removed the feature from the user interface and most likely its just buried away somewhere. Much like this one was taken away through the registry.
Auto arrange is your is feature that Microsoft has forced upon us in Win7 and here is how to turn it off. My fix turns it off Globally but you can do it whatever way you like.
Ill attempt to explain what these reg values do but some are still unknown.
I would like some confirmation on what some of the other keys do under this entry. So if you can help please do as some are still a mystery. Some of the keys below were in other versions of windows but have different values from previous versions of windows. For example FFlags is one that was but you can not use XP or vista FFlags values as they are different.
First navigate to this section of the registry. Then Delete the Bags key there. This will clear out all saved folder view currently stored in the registry.
Windows Registry Editor Version 5.00
;Delete all Bags entries, storing view settings first
;___________________________________________________
[-HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags]Bags can then be recreated either manually or just open up explorer and navigate to any folder. Refresh regedit and it will be back.
Then under Bags create \AllFolders\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}]
If you copy the above txt and the text below and you can do it all at once in a reg file. Just copy and paste the following into a txt file and rename to reg and import. For the newbies UAC will come up and ask you to confirm say yes.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}]Then you see the entry under that section and can navigated to in regedit.
What you have created there is the generic template folder. {5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}
One thing I am still trying to figure out is where in the registry these values are pulled if you do not set them like we are doing here. Since under customize this folder these templates get created with default MS values.
The Global template for folders are as follows.
{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7} =none specific
{7d49d726-3c21-4f05-99aa-fdc2c9474656} =Docs template
{94d6ddcc-4a68-4175-a374-bd584a510b78} =Music template
{b3690e58-e961-423b-b687-386ebfd83239} =Pics template
{5fa96407-7e77-483c-ac93-691d05850de8} =Video template
The templates above sets up how a folders view is interpreted in windows. Keep in mind the AllFolders entry used below does not exist in win 7 default unless you apply the template through customize this folder context menu or set them yourself. The edits to these templates are also applied moving forward to all folders you customize with the template. Where the MS default template originates in the registry is unknown. You can edit all of the templates in the way we are editing the generic template. The one difference is with the video template you get an option to hide/show file names. Other then that they are the same except how the files are shown.
[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}]
Entries under the above key and what they do:
“Rev”=dword:00000000 = When this is set to 0. I believe this is what actually causes auto arrange and align to grid to show in context menus. Need to confirm this as I'm not sure and no amount of googling has helped.
“FFlags”=dword:43000001 = auto arrange checked but showing. 43000000 turns it off for any folder the template is applied to.
“Vid”=”{0057D0E0-3573-11CF-AE69-08002B2E1262}” = the icon view used. See below (same as vista).
View Mode vid
Icons 1 {0057D0E0-3573-11CF-AE69-08002B2E1262}
List 3 {0E1FA5E0-3573-11CF-AE69-08002B2E1262}
Details 4 {137E7700-3573-11CF-AE69-08002B2E1262}
Thumbnail5 {8BEBB290-52D0-11D0-B7F4-00C04FD706EC}
Tiles 6 {65F125E5-7BE1-4810-BA9D-D271C8432CE3}
Filmstrip 7 {8EEFA624-D1E9-445B-94B7-74FBCE2EA11A}
“Mode”=dword:00000001 = Icon view as above (same as vista)
“LogicalViewMode”=dword:00000001 = Align to grid checked I believe. dword:00000003 makes it unchecked
“IconSize”=dword:00000030 Size of icons used. See below.
10/30/60/100 Small/Medium/Large/X-Large Icons
Icons view can use all Icon sizes. Tiles uses 30 on and details and list views use 10 only.
"Sort"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,30,f1,\
25,b7,ef,47,1a,10,a5,f1,02,60,8c,9e,eb,ac,0a,00,00,00,01,00,00,00
I believe this hex value under sort sets it to type but can not confirm this.
There are some other entries under this key.
ColInfo
GroupView
GroupByKey
GroupByDirection
I have no idea what they do in the template. However I believe colinfo controls the navigation on the left showing. If anyone knows what these do It would be interesting to know for ref.
If you want the icon view set to 30. Generic template set to all folders with Auto Arrange and align to grid off Globally. Here is the reg for that. Also includes a few other reg entries I use.
Windows Registry Editor Version 5.00
;Delete all Bags entries storing view settings first
;___________________________________________________
[-HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags]
;Get rid of windows not saving settings on exit if exsists
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"NoSaveSettings"=-
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"NoSaveSettings"=-
;Disbable full row select in windows 7
;______________________________________
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"FullRowSelect"=dword:00000000
;Disable sniff folder feature in Windows 7 and sets folder type to not specific
;______________________________________________________________________________
[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell]
"KnownFolderDerivedFolderType"="{57807898-8C4F-4462-BB63-71042380B109}"
"SniffedFolderType"="Generic"
"FolderType"="NotSpecified"
;Generic - Folder Template Global set because folder type is set to not specified above.
;First template is what is used for all types of files in windows
;Rev key when set to 0 shows Auto Arrange and Align to grid in menu
;FFlags turns off Auto Arrange when set to 43000000 and 43000001 is on
;Vid sets the type of file that is in the folder icons, list, thumbnail, tiles etc
;mode is the icon size used in vid 10/30/60/100 Small/Medium/Large/X-Large Icons
;Tiles vid uses 30 on and details and list views use 10 only.
;sort is how the folder is sorted. Type, name etc
;All templates can be set same as generic but can be modified if you decide to use them.
;_____________________________________________________________________________________________
[HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\Shell\{5C4F28B5-F869-4E84-8E60-F11DB97C5CC7}]
"Rev"=dword:00000000
"FFlags"=dword:43000000
"Vid"="{0057D0E0-3573-11CF-AE69-08002B2E1262}"
"Mode"=dword:00000001
"LogicalViewMode"=dword:00000003
"IconSize"=dword:00000030
"ColInfo"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,fd,df,df,fd,10,\
00,00,00,00,00,00,00,00,00,00,00,04,00,00,00,18,00,00,00,30,f1,25,b7,ef,47,\
1a,10,a5,f1,02,60,8c,9e,eb,ac,0a,00,00,00,10,01,00,00,30,f1,25,b7,ef,47,1a,\
10,a5,f1,02,60,8c,9e,eb,ac,0e,00,00,00,78,00,00,00,30,f1,25,b7,ef,47,1a,10,\
a5,f1,02,60,8c,9e,eb,ac,04,00,00,00,78,00,00,00,30,f1,25,b7,ef,47,1a,10,a5,\
f1,02,60,8c,9e,eb,ac,0c,00,00,00,50,00,00,00
"Sort"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,30,f1,\
25,b7,ef,47,1a,10,a5,f1,02,60,8c,9e,eb,ac,0a,00,00,00,01,00,00,00
"GroupView"=dword:00000000
"GroupByKey:FMTID"="{00000000-0000-0000-0000-000000000000}"
"GroupByKey:PID"=dword:00000000
"GroupByDirection"=dword:00000001Thanks
0 -
Yes it should be fixed, do you claim otherwise?
Yep it seems like it is. No errors so far in vmware. THANKS NUHI!!!
I hope there are none on a real machine. Should be the same though.
0 -
Interesting. I was just mentioning some problems I was having like this in another topic.
Back when Sp2 had come out. I noticed some strange differences between XP slipstreamed SP2 compared with MSDN XP SP2 pre-integrated discs used with nlite when removing the same things. I was also not using any other customizing apps. I would get very different results from the pre-integrated once installed. Some errors like this one but also internet problems. I eventually gave up and started using 2003.
Now I am back to XP with SP3 and I was concerned about those problems coming up again with pre-integrated Sp3 discs. I only have the pre-integrated disc to use so i hope that whatever happened back then nuhi has it figured out now. I did use your newest version 1.4.8 with my sp3 disc.
Can someone confirm who has also used a SP3 pre-integrated disc that this problem has been fixed in 1.4.8 and that there are no other issues that come up?
THANKS
0 -
So no one has a possible answer to this question. Has anyone tried SP3 slipstreamed and SP3 pre integrated with nlite and seen a difference once installed?
You may be one of the first to come across this problem. I figured things out by using a synchronizer, in my case ViceVersa Pro (you can download a trial).
-That gives you the exact difference between two installation sets. It is probably best to figure that out first.
I have beyond compare. I ran the comparison on SP2 integrated and Slipstreamed and there were differences but there were not many differences in the individual files compared. The differences were just dates on the files. However there were more files in the slipstreamed version as I recall. Now I have not done the same with SP3. The thing is the files that were missing from the pre-integrated SP2 did not seem to be very important. They were files for items I usually would remove with nlite anyway.
My conclusion was that even with the differences Nlite should not yield these strange results that I found. I believe the real issue here was the fact that some of the sif files and other files nlite edits were organized differently and that was causing the problems.
Has anyone else used a pre-integrated source with nlite and had any strange results? I would like to hear about it. I think there is something here.
0 -
I hope someone here can answer this for me.
Here is the situation. Back when SP2 came out I had slipstreamed SP2 from my SP1 source disk and then would use nlite on this to remove items. I had no issues with this with nlite or once installed.
I then downloaded a SP2 pre-integrated from Microsoft and used nlite on this iso. I removed the exact same things as I did with the slipstream copy. The differences were astonishing once the iso was installed & had some issues with nlite also. I had lots more issues once in the install. Issues with IE6, internet, wireless etc.
I came to the conclusion that clearly nlite was better with a slipstreamed SP disk then a pre-integrated one from MS. Must have something to do with how nlite looks at the source.
I am now wondering if this is going to be the same issue with SP3. I recently got a pre-integrated SP3 disc and I'm wondering if a slipstreamed disc from SP1 or SP2 would be better to use with nlite then a pre integrated SP3 one from MS?
Has anyone else had issues like this with pre-integrated discs from Microsoft and nlite? Please post if you have or have not had any issues especially with SP3 pre integrated. THANKS
So no one has a possible answer to this question. Has anyone tried SP3 slipstreamed and SP3 pre integrated with nlite and seen a difference once installed?
0 -
I hope someone here can answer this for me.
Here is the situation. Back when SP2 came out I had slipstreamed SP2 from my SP1 source disk and then would use nlite on this to remove items. I had no issues with this with nlite or once installed.
I then downloaded a SP2 pre-integrated from Microsoft and used nlite on this iso. I removed the exact same things as I did with the slipstream copy. The differences were astonishing once the iso was installed & had some issues with nlite also. I had lots more issues once in the install. Issues with IE6, internet, wireless etc.
I came to the conclusion that clearly nlite was better with a slipstreamed SP disk then a pre-integrated one from MS. Must have something to do with how nlite looks at the source.
I am now wondering if this is going to be the same issue with SP3. I recently got a pre-integrated SP3 disc and I'm wondering if a slipstreamed disc from SP1 or SP2 would be better to use with nlite then a pre integrated SP3 one from MS?
Has anyone else had issues like this with pre-integrated discs from Microsoft and nlite? Please post if you have or have not had any issues especially with SP3 pre integrated. THANKS
0 -
nuhi, why don't you make nLite an open source project? I would like to be able to help fix bugs, but as a closed software project this aint going to work.
I agree. Plus Nuhi you would have vlite to focus on more. Making nlite open source would take a lot of issues off your plate. I'm not a coder but I'd love to see how other people may take nlite in other directions. I hope you consider this idea.
GREAT RELASE with 1.4 THANKS for all the work. I have had no issues so far with it.
0 -
I dont use SFC either. I always apply your patch to stop that annoying feature so I know its not windows replacing the file back or anything like that.
Also there is no way I could not use component removal. As for the rest of the triggers the only other one I use is some of the patches for TCP/IP and SFC.
It might be something Im doing thats causing the problem Ill have to strip my disc off all my reg entries and other customizations to narrow it down.
THANKS for your help though.
If anyone else has this problem in 2003 can you please explain the situation and what if anything you did to fix it?
0 -
There is no secret, why are you constantly aiming towards that is beyond me.
Are you sure that the syssetup.dll is exactly the syssbck.dll now, did you overwrite it by hand?
Did you remove CAT files?
Nuhi,
1. In general what I'm getting at is I would like to understand some of the stuff that nlite does behind the scenes, the not so obvious things. Like a list of dlls it edits etc, or how they are edited. I think if more of this was understood by some of the members here we could better fix our own problems. OR find what were doing that is messing up nlite.
2. I checked both my syssetup.dll and syssbck.dll they are both correct & in my i386 before install, yet the replacement never happens by the nlite.inf during install. I am not sure why. I have even replaced the original sysssetup.dll back after the install and that does not fix the problem. I'm not sure why that is unless this dll has another dll that must also be replaced or needs to be re-registered or a reg entry also must be changed.
3. I do not remove the cat files. Like I said when you remove the cat files its like windows has no idea what the usb device is. This is different it knows what the device is but still forces you to install the device. Could the cat files be removed without checking that in nlite? and could this cause the setupapi.log errors I'm still getting about syssetup.dll (An unsigned, incorrectly signed syssetup.dll)
In any case is there any more that could be causing the problem? Or have i got it all?
THANKS
0 -
Madhits45,
how is it possible that that the line (movex syssbck ...) is missing from your nlite.inf?
Maybe you think that I should know that but it simply seems not possible, even though I hope that's the case and we find out why.
Do you (all with this issue of not having the restored file) run Windows by setup.exe (winnt32.exe) or use your own winnt.sif file or anything that would skip this portion?
Because by just using nLite with it's Unattended options should be fine.
NUHI.. There must be something else. I thought this line was missing from my nlite.inf.
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce","nlite_post_s05",0x00020000,"nhelper moveex ""%17%\syssbck.dll"" ""%11%\syssetup.dll"""
However it is there and I believe working. Yet I still get the errors in setupapi.log saying that my syssetup.dll is not signed. What else could be causing this? Does the dll need to be re-registered in order to work?
I do use my own winnt.sif file but it was one that was originally created by nlite. What line could be missing from that? nlite.inf is run from cmdlines.txt I thought. The entry for it is there.
I am stilling getting the pop up for common USB devices. Whats strange is they do mount and can be used but the pop up to install them comes up.
If you can share any more of your insight on how the nlite.inf does what it does, then I should be able to fix this issue on my own.
PLEASE LET ME KNOW>
THANKS
0 -
wondras, thanks. nLite should have done that on it's own, you can find the command in the nlite.inf.
But this helps a lot because I didn't know that the function failed for some reason, at least it will be easier to debug now.
Things which trigger syssetup patching are:
- patches
- component removal
- ie7 integration
- addons which edit syssetup.inf
Btw nLite backups clean syssetup.dll to the syssbck.dll in the i386 folder, just extract that, it should be the clean version. If it's not then that is the problem, maybe you ran nlite more than once and it didn't detect the clean version properly on the second run.
edit: tried it now with all removed and the backup was restored just fine. If someone finds out how to break this yell.
Also check windows\setuperr.log for errors, maybe your nlite.inf never got executed if something else broke before it.
NUHI... THANK YOU, THANK YOU :-). This is the kinda info I have begged you for in the past with regards to how nlite does things. I know you don't wanna give away all the secrets but MAN is this kinda info is VERY useful.
I have determined that in my windows 2003 disc that the syssbck.dl_ is the original. The nlite.inf is not replacing the original file back in my case. Nlite.inf is executed from cmdlines.txt. Its done with this line in cmdlines.
"rundll32 advpack.dll,LaunchINFSection nLite.inf,nLiteReg"
I did change the order of this file and made yours last. This I dont believe can cause an issue. I found the line that replaces the sysetup.dll was missing from my nlite.inf. That was my problem. THANKS
I will look through the nlite.inf and see what else might be missing.
THANK YOU AGAIN.. problem solved.. now time to test it out.
0 -
Fixed this weird error in the next version.
It happened only on some special Windows version, I mean that single file was different than on mine or the majority of Windows out there. That's why this wasn't known before. Got this report 3 times so far. And it is fixed so don't worry you won't be sick of it any more.
Madhits45, you're making no sense. nLite is most famous for it's textmode driver integration.
sorry nuhi I never used it. Just don't like to put all eggs in one basket. Usually if an install has a problem its easier to find it between the various apps you use then one app that does it all & could have multiple possible areas that could be causing it. Nlite does so much and since I have had issues that approach basically helps me narrow them down.
0 -
I know get the Mass Storage driver pack and integrate that using driverpacks base. Nlite is primarily for removing things. Keep it simple and use driverpacks, plus the compression is better with driverpacks.
0 -
Two words. Driverpacks & google
0 -
That is really strange. I believe it has to do with the registry not being completely created at the time your installing the apps as part of addon's. I believe the current user hive is created after updates are done (svcpack addons). The reason it would work at run once is because the apps are changing the registry after its all setup. Do you have conflicting apps that install after your addon apps? Ones that might be stealing the associations?
I myself don't install apps as part of SVCpack any longer due to other strange issues. Theres not much of a difference if you do it during runonce if its all silent anyway.
0
Win7 packages
in vLite
Posted
I'm looking for this also. Ive got packages.xls but it cant be right. Some of the info is clearly wrong.