Jump to content

thuun derboy

Member
  • Posts

    111
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by thuun derboy

  1. to use just a single cmd to perform the diskpart funtions; try somthing like... @echo off ver set script=%temp%\vdisk.txt >"%script%" echo create vdisk file=c:\Win7_x86.vhd maximum=%1 >>"%script%" echo select vdisk file=c:\Win7_x86.vhd >>"%script%" echo attach vdisk >>"%script%" echo exit diskpart /s "%script%" info on above: cmd is part of my windows 7 vhd based setup script placed in the pe system32 dir.
  2. XP SP3 Has a BLACK SCREEN OF DEATH.
  3. Awsome guide, really good! I found CA_BlockDirectInstall_Cartman_MSI twice.
  4. thanks so very much, Gosh! I have been working on a set of component removal batches/infs for xp, so I can't wait to see your discoveries! --wondering if you also have an infOptional dir. somewhere! Too bad more people don't enjoy using nt cmd shell based tools, it's to be expected though.
  5. Using MS BDD is the approved method, one can also find the old ximage.exe to mount the old format and slice and dice a longhorn setup to achive this. I'm doing something similar now. I wound up looking at how the early longhorn builds were converted (by members here and elsewere) to use the i386 dist folder and winnt.sif for ua setup, this helped me to uderstand more possibilities. Suggest you google winflp and check out the old winfx runtimes also.
  6. In winnt.sif (unattend.txt) you may specify the default theme. Try pointing it at the classic theme. ( or any theme file ) [Shell] CustomDefaultThemeFile = "%WinDir%\Resources\Themes\Windows Classic.theme" It may work. I usually remove luna manually or using nlite (much faster), or, swap it for the Zune theme.
  7. @arjuna07 What your trying to do is not difficult if your interested, just time consuming. While you work on it, think about how you'll undate the finished image. Keep folders you use to create silent setups, configuration files, etc. for adding to a ua template, if so inclined.
  8. WinFLP sounds interesting. I'lll search for more details, thx.
  9. And currently, this leads to a problem if nlite is left to just run a default course. You must use a little logic applied to some clicks of the up / down arrowns in the hotfix ui. <-- This feature is essential if nite is to work for builds a few months after it's release. Thx for the cmd-line support Nuhi! Regards, -t
  10. thx to jaclaz for pointing me here... I too am trying to setup XP from USB (without PE or DOS assistance). Searching just now I found THIS. It's called 'Flashboot' and is buried in side the nlite addon. I can't say more but will test it out later and see what's up. It has an option to convert a bootable iso image to a bootable USB device. Perhaps this combined with 'SetupSourceDevice' altered in txtsetup.sif will work, who knows. I do have a feeling the answer to this one is more obvious than one might think. I would like to think grub isn't required for this task. -- upd -- flashboot is shareware and only makes boot disks out of isolinux and floppy based images, oh well, the search is on again.
  11. I used IE7 beta then final, the last ver. makes many troublesome changes to core components of explorer causing problems for some users. I'm sticking with IE6 and Opera for everyday use. I'm reminded at WinUpdate to install but take WU w/ a grain of salt.
  12. XP on xp behaving odd as always, networking and audio issues on most setups.
  13. just add your password... AdminPassword=yourpassword couple thoughts, using * is not recommended, it's used for blank password Windows 2000 requires that you enter a password in the answer file for autologon, XP does not. If you don't include a logon count entry it allows unlimited autologon. (W2K) hope that helps.
  14. I'm certain there must be a few interesting discoveries left. Hoping some of you might like to share what you've found that's not included in ref.chm. I'd like to put together a collection of all the undocumented components entries for W2K/XP (many good ones found at msfn).
  15. death comes ripping think first. -- thx. nuhi.
  16. yes, pe is very helpfull in that way. however, today i seek a way to run a self contained xp setup from usb. It involes adding the required boot-sector...copying source files to usb obviously, and some modifications to txtsetup.sif, changing SetupSourceDevice perhaps. hmm...
  17. as many undocumented component entries as posible...
  18. Microsoft has a guide on this, they pretty much suggest you install from behind a firewall and activate over the internet using info placed in winnt.sif, i think. (it's vol lic. for me.). Google is your friend, try a search.
  19. there's a utility called double driver, it's freeware, extremely effective and used by the PE community for some time. It's my personal choice anyway.
  20. the winpe opk is for users that understand the basic framework of windows xp and it's setup, a user say that's taken time to review all the help materials etc. if the setup manager is too dragged out, btw, aint gonna spit out any iso no matter how hard you whack it, you might want to just use pebuilder to make your 'live' cd. best o luck.
  21. I'm such a doof. I have it working now with files from a few diff. versions of Vista (latest release fbwf has caused bsod). and thx. for info. on Embedded SP2 Feature Pack 2007. I just downloaded it.
  22. As of October's updates (to Offfice 2K3), office shink no longer works. It had been skiping a handfull of files that I kept track of and added manually in past months. However, one of the recent .msp patches has really thrown the office shrink autoit script off, too bad. And, with no update in 2 yrs.... I guess the creator is long gone. If any one feels like assisting, I'm about to decompile shrink_lang02.exe. My autoit skills at this point are weak but may be improoving shortly. I may rewritre as a batch as I don't care about cosmetics, well see what the decompiler spits out. In recent months updates have increased and it's difficult to track down which one(s) are causing this process to fail. I doubt anyone knows right now (only yesterday was patch Tues.). Here's a tested, complete list of required patches should it proove to be usefull.... E:\OfficeUpdater\Office_Updates\SP2 ================================== MAINSP2ff.msp 95103 KB OWC11SP2ff.msp 6071 KB Total 2 file(s); Size: 103602688 Byte(s) E:\OfficeUpdater\Office_Updates\KB892843 ======================================= OLKINTLff.msp 3914 KB OUTLOOKff.msp 9138 KB Total 2 file(s); Size: 13366272 Byte(s) E:\OfficeUpdater\Office_Updates\KB894542 ======================================= MSPUB.msp 5084 KB Total 1 file(s); Size: 5206528 Byte(s) E:\OfficeUpdater\Office_Updates\KB907417 ======================================= OTKLOADR.msp 2815 KB Total 1 file(s); Size: 2883072 Byte(s) E:\OfficeUpdater\Office_Updates\KB914455 ======================================= GPFILTff.msp 497 KB Total 1 file(s); Size: 509440 Byte(s) E:\OfficeUpdater\Office_Updates\KB920103 ======================================= INFOPATH.msp 4471 KB Total 1 file(s); Size: 4578816 Byte(s) E:\OfficeUpdater\Office_Updates\KB921566 ======================================= MSO.msp 12004 KB Total 1 file(s); Size: 12292096 Byte(s) E:\OfficeUpdater\Office_Updates\KB923088 ======================================= EXCEL.msp 14143 KB Total 1 file(s); Size: 14482944 Byte(s) E:\OfficeUpdater\Office_Updates\KB923091 ======================================= POWERPNT.msp 10016 KB Total 1 file(s); Size: 10256384 Byte(s) E:\OfficeUpdater\Office_Updates\KB923094 ======================================= WINWORD.msp 13416 KB Total 1 file(s); Size: 13737984 Byte(s) E:\OfficeUpdater\Office_Updates\KB923095 ======================================= OUTLFLTR.msp 5054 KB Total 1 file(s); Size: 5175808 Byte(s) E:\OfficeUpdater\Office_Updates\KB923097 ======================================= STLIST.msp 6106 KB Total 1 file(s); Size: 6253056 Byte(s) E:\OfficeUpdater\Office_Updates\KB924424 ======================================= MSXML5.msp 8079 KB Total 1 file(s); Size: 8272896 Byte(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Total 13 folder(s); 15 file(s) Total files size: 196 MB; 195916 KB; 200617984 Bytes ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Here's a simple batch i use to apply the patches: TITLE Micro$oft Office 2003 .MSP patch integration color f9 MODE CON: COLS=65 LINES=15 CLS @echo off ECHO. ECHO. ECHO Office 2003 Updater is ready to begin. ECHO. pause ECHO. ECHO Applying Service Pack 2 msiexec /p e:\OfficeUpdater\Office_Updates\SP2\MAINSP2ff.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb msiexec /p e:\OfficeUpdater\Office_Updates\SP2\OWC11SP2ff.msp /a e:\OfficeUpdater\Office_Source\OWC11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying 2 Post SP2 Updates from KB892843 msiexec /p e:\OfficeUpdater\Office_Updates\KB892843\OLKINTLff.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb msiexec /p e:\OfficeUpdater\Office_Updates\KB892843\OUTLOOKff.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB923095 msiexec /p e:\OfficeUpdater\Office_Updates\KB923095\OUTLFLTR.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB907417 msiexec /p e:\OfficeUpdater\Office_Updates\KB907417\OTKLOADR.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB914455 msiexec /p e:\OfficeUpdater\Office_Updates\KB914455\GPFILTff.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB920103 msiexec /p e:\OfficeUpdater\Office_Updates\KB920103\INFOPATH.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB921566 :: PVMSO.msp not for this version msiexec /p e:\OfficeUpdater\Office_Updates\KB921566\MSO.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB894542 msiexec /p e:\OfficeUpdater\Office_Updates\KB894542\MSPUB.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB923088 msiexec /p e:\OfficeUpdater\Office_Updates\KB923088\EXCEL.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB923091 msiexec /p e:\OfficeUpdater\Office_Updates\KB923091\POWERPNT.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB923094 msiexec /p e:\OfficeUpdater\Office_Updates\KB923094\WINWORD.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB923097 msiexec /p e:\OfficeUpdater\Office_Updates\KB923097\STLIST.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Applying Post SP2 Update KB924424 msiexec /p e:\OfficeUpdater\Office_Updates\KB924424\MSXML5.msp /a e:\OfficeUpdater\Office_Source\PRO11.MSI SHORTFILENAMES=TRUE /qb ECHO. ECHO Office SP2 and all updates applied. ECHO. ECHO Ready to exit, pause EXIT Ideas welcome.
  23. Nuno is saying if you use the trial of srv2k3 you'll get the same build as with the retail verson, and no need to download some warez AIO CD. Now that's pretty cool.
  24. easy there mate. MicroSawft uses a special sfx cab tool to make their service packs and one's best bet is to acquire a copy. Not so imposible, just have to know someone as it's not for dist. This is discussed on the 1st page of the unoff. SP5 thread. I seriously doubt this project was completed by deflating an archive and repacking it, I just can't see it, MD5 checks and all, but hey, I've been wrong before. Anyway, I do feel the point about the bugs in the pack, too bad eh?, but a def A+ for effort and oem mock-up.


×
×
  • Create New...