piXelatedEmpire Posted June 1, 2006 Share Posted June 1, 2006 (edited) 100_Cleanup.vbsThe first thing that is done is that up to two 7-Zip archives are decompressed. If 101_AllUsers.7z is found, it will be decompressed to %AllUsersProfile%. In some circumstances I throw in some shortcuts to Start Menu or the Desktop folders. If 101_ProgFiles.7z is found, it will be decompressed to %ProgramFiles%. If a registry file named 101_Registry.reg is found, it will be merged.Any chance you could share an example of these files? 101_AllUsers.7z - I wish to see how you have set this up if possible Edited June 1, 2006 by piXelatedEmpire Link to comment Share on other sites More sharing options...
RogueSpear Posted June 1, 2006 Author Share Posted June 1, 2006 Here you go...101_AllUsers.7z Link to comment Share on other sites More sharing options...
maxximum Posted June 2, 2006 Share Posted June 2, 2006 I've made a little script to change CD-rom drive letters.It has to be run as the last script as it changes CD drives order.ChangeCD_RomDriveLetters.zip Link to comment Share on other sites More sharing options...
Yurek3 Posted June 4, 2006 Share Posted June 4, 2006 (edited) I try now in new BTS DriversPack 6.5 for me work.I did change presetup.cmd likie thisSET TAG=\WIN51IP.SP2FOR %%i in (c d e f g h i j k l m n o p q r s t u v w x y z) DO IF EXIST "%%i:%TAG%" SET CDDRIVE=%%i:SET OEM=%CDDRIVE%\OEMIF EXIST %OEM%\7za.exe Copy %OEM%\7za.exe %SYSTEMROOT%\system32\7za.exeIF EXIST %OEM%\DP*.7z 7za.exe x -y -aoa %OEM%\DP*.7z -o%SYSTEMDRIVE%IF EXIST %SYSTEMDRIVE%\DP*.7z 7za.exe x -y -aoa %SYSTEMDRIVE%\DP*.7z -o%SYSTEMDRIVE%IF EXIST %SYSTEMDRIVE%\DP*.7z DEL %SYSTEMDRIVE%\DP*.7zIF EXIST %OEM%\000_WinDir.7z 7za.exe x -y -aoa %OEM%\000_WinDir.7z -o%SYSTEMROOT%IF EXIST %SYSTEMDRIVE%\000_WinDir.7z 7za.exe x -y -aoa %SYSTEMDRIVE%\000_WinDir.7z -o%SYSTEMROOT%IF EXIST %SYSTEMDRIVE%\000_WinDir.7z DEL %SYSTEMDRIVE%\000_WinDir.7zIF EXIST %OEM%\000_SystemDrive.7z 7za.exe x -y -aoa %OEM%\000_SystemDrive.7z -o%SYSTEMDRIVE%IF EXIST %SYSTEMDRIVE%\000_SystemDrive.7z 7za.exe x -y -aoa %SYSTEMDRIVE%\000_SystemDrive.7z -o%SYSTEMDRIVE%IF EXIST %SYSTEMDRIVE%\000_SystemDrive.7z DEL %SYSTEMDRIVE%\000_SystemDrive.7zIF EXIST %OEM%\SetDevicePath.exe SET SDP=%OEM%\SetDevicePath.exeIF EXIST %SYSTEMDRIVE%\SetDevicePath.exe SET SDP=%SYSTEMDRIVE%\SetDevicePath.exeIF EXIST %OEM%\WatchDriverSigningPolicy.exe SET WDSP=%OEM%\WatchDriverSigningPolicy.exeIF EXIST %SYSTEMDRIVE%\WatchDriverSigningPolicy.exe SET WDSP=%SYSTEMDRIVE%\WatchDriverSigningPolicy.exeIF EXIST %CDDRIVE%\D SET DP=%CDDRIVE%\DIF EXIST %SYSTEMDRIVE%\D SET DP=%SYSTEMDRIVE%\DIF EXIST %CDDRIVE%\OEM\bin\7z.exe x -y -aoa %CDDRIVE%\OEM\bin\finish.7z -o"%SystemDrive%" COPY /Y %CDDRIVE%\OEM\bin\cmdow.exe %SystemDrive%IF EXIST %CDDRIVE%\OEM\bin\7z.exe x -y -aoa %CDDRIVE%\OEM\DP*.7z -o"%SystemDrive%"IF EXIST %CDDRIVE%\OEM\*.ins COPY /Y %CDDRIVE%\OEM\*.ins %SystemDrive%IF EXIST %CDDRIVE%\OEM\bin\DevPath.exe %SystemDrive%\D%SDP% %DP%START %WDSP%START %CDDRIVE%\OEM\bin\WatchDSP.exeEXITlooks in folder OEM is like thisTHX a lot sir RogueSpearYurek3 Edited June 4, 2006 by Yurek3 Link to comment Share on other sites More sharing options...
piXelatedEmpire Posted June 4, 2006 Share Posted June 4, 2006 Here you go... fantastic thank you very much RS Link to comment Share on other sites More sharing options...
hosebeast Posted June 5, 2006 Share Posted June 5, 2006 I've changed 070_VMwareTools.vbs, as VMtools are differents and incompatible between VMware workstation 5.5.1, server 1.0 and GSX 3.2.1.I knew they were different but why do you say they are incompatible? I have an XP Pro VM running in Workstation 5.5.1 which I upgraded from Tools 19175 (the latest build from Workstation 5.5.1) to 24927 (the build which comes with Server 1.0 RC1) and everything seems to be working fine under Workstation 5.5.1. The service starts, mouse capture/release is automatic, all features of the tray icon works, no errors are logged in the Event Log, nothing looks unusual at all. Link to comment Share on other sites More sharing options...
serterkek Posted June 7, 2006 Share Posted June 7, 2006 Hello All,First of all brilliant work RogueSpear,My guestion is how can you make post install more secur, for instance while application is installing someone can interrupt installation, is there any way you can lock during installation.Thanks Link to comment Share on other sites More sharing options...
maxximum Posted June 8, 2006 Share Posted June 8, 2006 I knew they were different but why do you say they are incompatible? I have an XP Pro VM running in Workstation 5.5.1 which I upgraded from Tools 19175 (the latest build from Workstation 5.5.1) to 24927 (the build which comes with Server 1.0 RC1) and everything seems to be working fine under Workstation 5.5.1. The service starts, mouse capture/release is automatic, all features of the tray icon works, no errors are logged in the Event Log, nothing looks unusual at all.I've tried with GSX 3.2.1 and VMtools from Server 1.0 .... and it does not work very well. I use VMtools included in differents VMware versions. Maybe VMware workstation 5.5.1 is more "tolerant" to latest VMtools than GSX Server 3.2.1 !My guestion is how can you make post install more secur, for instance while application is installing someone can interrupt installation, is there any way you can lock during installation.Create a new script with this code :On Error Resume NextSet objShell = CreateObject("Wscript.Shell")objShell.Run "%windir%\System32\rundll32.exe user32.dll,LockWorkStation" Link to comment Share on other sites More sharing options...
piXelatedEmpire Posted June 15, 2006 Share Posted June 15, 2006 100_Cleanup.vbsThe first thing that is done is that up to two 7-Zip archives are decompressed. If 101_AllUsers.7z is found, it will be decompressed to %AllUsersProfile%. In some circumstances I throw in some shortcuts to Start Menu or the Desktop folders. If 101_ProgFiles.7z is found, it will be decompressed to %ProgramFiles%. If a registry file named 101_Registry.reg is found, it will be merged.So, let's get into the settings.[Cleanup]CleanAllUsersStartMenuYN=YesCleanUserStartMenuYN=YesDelWindowsCatalog=YesDelSetPrograms=YesDelMovieMaker=YesDelAccAccessibility=YesDelAccCommunications=YesDelAccEntertainment=YesDelAccSystemTools=YesThese entries all have to do with the Start Menu. All of the entries beginning with "Del" indicate shortcuts or subfolders of Accessories that are to be deleted from the All Users Start Menu and are dependant on the CleanAllUsersStartMenuYN entry. The CleanUserStartMenu entry when enabled deletes all shortcuts and the Accessories subfolder from the User Start Menu. This will not prevent creation of shortcuts to the User Start Menu from the registry (ex: \Accessories\Address Book).If my understanding of this particular script is correct, when the 101_AllUsers.7z is decompressed it wont actually delete anything from the Start Menu just add whatever is within the 7z file?Therefore the only way to delete things from the Start Menu is with the CleanAllUsersStartMenuYN=Yes command and following Del statement?Basically what I am saying is is it possible to create a custom AllUsers.7z that will completely overwrite the default Start Menu (delete everything from it) and only install what is within the AllUsers.7z?I hope that made sense Link to comment Share on other sites More sharing options...
RogueSpear Posted June 15, 2006 Author Share Posted June 15, 2006 No, the decompression of the .7z file is just that.. decompression. What I've though about is adding an option to completely 100% delete the All Users Start Menu. Then it would be up to the user to include everything that they need in the .7z file. Link to comment Share on other sites More sharing options...
piXelatedEmpire Posted June 15, 2006 Share Posted June 15, 2006 I'd be very interested in knowing how to completely delete the All Users Start Menu and replacing with a complete custom one Link to comment Share on other sites More sharing options...
RogueSpear Posted July 12, 2006 Author Share Posted July 12, 2006 Version 1.03 is released and can be found here.While very long overdue, this release is not very big on new features but there are a lot of changes to maintain compatibility with Bashrat the Sneaky's DriverPacks and to blend in with AutoImage. And of course there are some improvements and bug fixes.I have a few ideas for new features to be implemented in v1.04 which should not take nearly as long now that the major changes and testing with AutoImage have been completed. Link to comment Share on other sites More sharing options...
Yurek3 Posted July 19, 2006 Share Posted July 19, 2006 (edited) I use your Script Pack for instal few aplikatons.This is very interesting metodi did put in 7zip file programs after instalation and registrations andactivationsfrom file Programs File to 101_Prog.7z, from Windows\system32 to 000_WinD.7z , from Documents and Setings to 000_Syst.7z and Menu Start to 101_AllU.7z and .reg for apllications from registry.This is OEM dorectoryHere101_Prog.7z101_AllU.7z000_WinD.7z000_Syst.7zAfter instalation I got all programs in my Menu Start and all work goodYurek3 Edited July 20, 2006 by Yurek3 Link to comment Share on other sites More sharing options...
ideas Posted July 28, 2006 Share Posted July 28, 2006 GREAT SCRIPTS Link to comment Share on other sites More sharing options...
ideas Posted July 28, 2006 Share Posted July 28, 2006 are u planning on posting new & improve ones? Link to comment Share on other sites More sharing options...
.jpg.fcda2bf67102e99518e8eab7f95dfbce.thumb.jpg.45162c26daae8896bead83391b9ed5b1.jpg)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now