edmoncu

bump, i hope someone could help me...

also if the bios it uses is award-based. you can use winflash to flash under winxp. i believe there's a separate tool for ami-based bioses as well that does the same.

hi... i would like to ask a follow-up question if its okay. i would like to set the default settings for all users (HKLM or HKU) to be like this. however, most of the settings available i have seen so far were applied only to the current user (HKCU). and upon looking at the equivalent HKLM settings, folder settings are divided into subsections (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder). i am kinda confused at how to set things there... any help would be greatly appreciated. thanks in advanced. anyhow, here's what i wanna set for all users on the folder options leaving other options at their defaults: - Display the contents of system folders - Do not cache thumbnails - Hidden files and folders Show hidden files and folders - Not to Hide extensions for known file types - Not to Hide protected operating system files - Not to Remember each folder's view settings - Restore previous folder windows at logon - Show Control Panel in My Computer - Show encrypted or compressed NTFS files in color - Show pop-up description for folder and desktop items - Use simple file sharing Again, thank you very much in advanced and more power.

the site you're referring doesn't work.

hi bts, are you referring on running regedit directly from the cmdlines.txt? should i also include these when i add to registry? [HKEY_CURRENT_USER/Control Panel/Desktop] "MenuShowDelay"="0"

yups. i have only placed the relevant entries. sorry if the code is incomplete... will edit it now

Hi, I was wondering, if there's a way to set the same menushowdelay (or any similar settings from the HKEY_CURRENT USER) settings for all existing and future users of my machine via registry. I have tried this: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER/Control Panel/Desktop] "MenuShowDelay"="0" But it only affected the current user... I have also tried this: Windows Registry Editor Version 5.00 [HKEY_USERS/.DEFAULT/Control Panel/Desktop "MenuShowDelay"="0" But it didn't worked either. Thanks in advanced for your replies.

bump will unattended joining to the domain work with winnt.sif on an unattended cd?

i was wondering, does winxp pro already support software-based raid5? or do i still need these modified files that the site i mentioned tells?

sorry for the late response, but do you mean XP Pro already has that feature?

will this work with an unattended cd? i tried experimenting with it, but after the installation point where xp is configuring network settings, it shuts down the installation of xp and restarts and goes that way... much like an endless loop.

may i know where can i obtain that one? thanks a bunch

hi. when i manually install SAV9 to my machines, i was instructed to install it as "managed" (not standalone) setup... i was wondering, with silent install of SAV9 discussed here, what kind of client install does this one do, managed or unmanaged or standalone? if ever, how will i silently install this one as "managed"? thanks a bunch.

@muevelonyc: btw, i did not see txtsetup.inf, instead, i saw txtsetup.sif and i edited that instead (but it gave me errors of missing files)... care to clarify what files to edit? thanks a bunch. also, when i extracted the BTS' mass storage driverpack, there were a couple of files having the same name... should i just overwrite some duplicates? thanks. i would like to clarify the steps you outlined... coz im a bit confused - so, first, decompress the BTS mass storage and isolate all the *.SYS files - copy all the *.SYS files to the i386\system32\drivers or minint\system32\drivers folder - paste to add the codes you posted to the txtsetup.inf (or is it the txtsetup.sif) file ---------------------------------- update: now i realized what was wrong... there were actual missing files to the code that you posted... and these are... what i did is rem'ed out all the lines you posted that contains references to these files. after that, bartpe booted from the cd normally. anyways, i used the latest version (as of this date, its 5.03) of BTS' mass storage driver pack. i've also attached a file that contains the entry to be added to the txtsetup.sif file that corresponds to BTS' mass storage driver pack... just paste that at the end of the txtsetup.sif file that BartPE creates. please feel free to comment if what i did is safe to the functionality of the cd. txtsetup.sif_entries.zip

even as i moved the *.sys files onto the \i386\system32\drivers, its still giving me the same errors upon bootup.

bump still getting the same errors...

wow cool! may i know the differences between pack A and pack B? thanks

yup, i did tried your manual fix and it solved the problem. thanks very much!

Hi Bâshrat, Just tried the 5.02.27 (and all updated driverpacks) with method 2 and everything seemed to go well. However, when I tried to install the iso in VMWare, at the first reboot after t-0, the familiar windows screen shows up, after a second followed by a BSOD. It keeps coming back and it soesn't matter whether I try safe bootmode or not. I'll try to find out more on this error, but maybe you have some ideas on it ? Moe ← same thing happened with my setup... wonder what went wrong... - used method1 on integration - nforce2ultra400 (epox ep-8rda3+) - raid/nvraid is disabled, parallel ata used - bsod at t-0 (starting windows on textmode setup) on vmware its okay... i used the latest driverpacks on my setup...

hi, nice guide! but when i tried it i got an error booting on my cd...

mrjojo, i encourage you to try using autoit's window-spy program so you will know exactly the detailed parameters of the window you are applying the script with (window title, button variable, etc). perhaps, there could be some hidden words or alike that you have omitted at specifying the window... remember, some buttons need to be very detailed (like in the case of "next >>")... each character matters when specifying details of a window or a message box. otherwise, the variable that controls "button3" under the "controlclick" command maybe referencing another variable. as for the serial# thingy, the registry method works well as long as you are using a legit key (w/c of course you bought)

BTS: hi, is this normal? i was wondering if you were referring to this one up. if it is not what it should be, should i rename this? if so, what name should i name this with? thanks. notice that the extension is not .exe or even .ex_ (compressed). the file size is 597kb though.

hi bashrat, im still having exactly the same problem with the latest version on the part where it recompresses the drivers... even if i only have the mass storage driver to process. CORRECTION: about the compression thingy... i realized the problem might have been associated where the entire folder was placed. i originally do stuffs at my desktop (w/c has a long path already). i tried placing the entire driverpack base folder on the root of my working windows partition and guess what, it ran fine. as for the no internet connection thing... i realized it only happens once you try to re-run the UpdateChecker_V5027.cmd which already has downloaded the Get_update.cmd. so far, i guess what's to be done for now with this is to edit Get_update.cmd and find this line SET NV=V5026 and replace the 5026 with 5027, save it and re-launch Get_update.cmd. CORRECTION (update): i believe was wrong. i now encounter the same error other guys were experiencing as well... the compression portion halted at the part about ctzapxx.exe something Compressing mgabg.exe... Utility.exe==CTZAPXX.exe was unexpected at this time.

hi bashrat. method 1 produced an error to me as the batchfile on the part where it should re-compress the extracted drivers. the message was and it goes back to the command prompt.altho this one's lesser of a problem, but clicking on UpdateChecker_V5027.cmd, produced an error saying it wasnt able to find UpdateChecker_V5026.cmd file. i tried running the update checker on the older package (with UpdateChecker_V5026.cmd as well as the DriverPack_MassStorage_V502.7z) and it said that all packages were already updated. i suppose this one may have to wait yet for an update from the remote side (w/c is very understandable).

before integration, i run update_v013.cmd file, and after it finishes, run the update_v015.cmd file. re-integrate it and everything seemed to work well.