sleepnmojo

Type the command set. That should give you a list of all the variables you can use. Usually when installing windows you have a smaller subset of these variables. As for your the path you posted, that can be shortened to %APPDATA%\Opera\Opera\profile\opera6.adr Also don't forget about the %ALLUSERSPROFILE%, where many programs put shortcuts, and other useful information.

Thats how I have it set up, a section for disable, manual, and auto. Then if I wanted to make one manual, I would just move it from the section it is currently in, and modify the value at the end to %MANUAL%. Here is where I go. When I work on an inf, and I have a question, this would be the site I reference. If you are starting out, I'd also recommend gosh inf tutorial. Gosh hasn't been around for a while, and I don't think he answers questions anymore, so posting on the board would be your best bet.

I have a string for each setting: auto, manual, and disabled. So if I want to change one from auto to disable I would just change %AUTO% to %DISABLED%. If you want to do the same just add an extra string. Add the following to your Strings section DISABLED=0x00000004 You can shorten that to just 4, but I like the long hex way .

Sorry to break it to you, but gosh hasn't been active for exactly 1 year now, so any response from him will most likely be silence. That is correct. They have nothing to do with the installation of windows. There are some cool stuff in those folders, but most people don't look there.

Did you get the cd from an OEM, like dell or hp (basically where did you get the cd)? Also, post your winnt.sif file if you have one (Don't forget the codebox tags). When are you noticing the file; is it after you install stuff, or first boot up? It looks like you slipstreamed a sp2 on a pro sp1 cd. Did you do the slipstream? The more info you give about your installation, the more we can help you. If people on this board seem a little pushy, it is because they are trying to answer your question, but you are telling them they are wrong, without helping them help you.

Looking at the posts, everyone told you what the culprit was, yet you blew them off like they were idiots. Finally someone explained to you exactly what was happening, and you finally accepted it. Don't get angry at Alanoll, he said the same thing over and over again. You chose not to listen. If you want to know what is installing the files, look at the list of files you are installing. Find out which one uses the installshield installer, and that is your most likely culprit.

This would be my stripped down version. How are you calling the inf? [Version] Signature="$Windows NT$" [DefaultInstall] AddReg=Services.Auto [Services.Auto] HKLM, %Services%\Messenger, "Start", %REG_DWORD%, %AUTO% [Strings] Services = SYSTEM\CurrentControlSet\Services AUTO = 0x00000002 REG_DWORD = 0x00010001 Make sure there are no quotes around the last section, it seems to screw up with them on the rundll command. Make sure you are using 128 also.

I don't see how a company = an individual, maybe you mean google will be another microsoft As for google, they are more like yahoo. I'm just waiting till they turn into another yahoo, and then another search engine emerges that overshadows all of them again.

sorry, double post

I haven't tested this yet, but I noticed this key changed when clicking the box REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion] "NoWarnPattern"=hex:23,04,12,00,00,00,00,00, Then try deleting it, after install, to re-enable it so the user would know to update. Edit: bad code tags

I don't know if you want to parse each user, but that would just mean an extra for loop, but this would get every profile for the current user. The cmd would save the 7z files next to the cmd file, where you could keep the 7zip executable if you wish, but I remark of the different ways of doing it. Also made editing the list file a little easier. @ECHO OFF REM Add the path to the 7zip executable SET PATH=%PATH%;"%ProgramFiles%\7-zip\" REM or leave it beside this cmd file SET PATH=%PATH%;%~dp0 REM the list of files to backup ( ECHO bookmarks.html ECHO cert8.db ECHO cookies.txt ECHO defaults.ini ECHO formhistory.dat ECHO hostperm.1 ECHO inforss.rdf ECHO inforss.xml ECHO key3.db ECHO localstore.rdf ECHO mimeTypes.rdf ECHO prefs.js ECHO search.rdf ECHO secmod.db ECHO signons.txt ) > %TEMP%\listfile.txt REM save all the profiles in the profile directory FOR /d %%D IN ("%APPDATA%\Mozilla\Firefox\Profiles\*") DO ( PUSHD %%D 7zA a -t7z "%~dp0\%%~nD.7z" @"%TEMP%\listfile.txt" -mx9 POPD )

nice find

Just a hint, when using the %ProgramFiles% variable, you will most likely need to use quotes around it. "%ProgramFiles%\MyProgram\program.exe" /command xcopy C:\moo\ "%ProgramFiles%\stuff" Those are some examples. Now some things commands need the quotes, while others don't. This is a good reason to test out the commands first.

I know what .default is, and it is not what you describe. You are confusing .default with the default user, like so many other people on this board. They are two very different things. There really needs to be a FAQ about this somewhere. I'm getting tired of seeing it everywhere. .default - login session, located at HKU\.default default user - located at %PATHTODOCSANDSETTINGS%\Default User (usually), needs to be loaded in order to edit. Please people for the love of God, please understand this. I talk about it more in this thread <{POST_SNAPBACK}> With all due respect, you're wrong. They're the same thing. Go ahead and try putting an entry in HKU\.Default\ (preferably in Software\Microsoft\Windows\CV\Run\ because certain types of accounts don't import all of the registry keys). Afterwards, create a new account. Log into that account and you'll notice that the registry info that you put in HKU\.Default will now be in HKCU. If you don't see your string there, you've done something wrong. Now, do the same thing, except instead of putting an entry in the registry, try putting a file in \Documents and Settings\Default User\. Create an account. Log into that account. Now that file should be located in %userprofile%\. If you don't see the file, you've done something wrong. If that's not enough proof for you, I will gladly provide you with a video in which I will execute all of the aforementioned commands. That is, under the condition that you will provide me a host for the said video. <{POST_SNAPBACK}> OK, here is your test, first you have to load the default user registry hive (I call it default). Import this reg file, and restart. Windows Registry Editor Version 5.00 [HKEY_USERS\default\Software\sleepnmojo] "b"="" "is"="right" [HKEY_USERS\default\Software\sleepnmojo\larry] [HKEY_USERS\.DEFAULT\Software\sleepnmojo] "a"="" "is"="wrong" [HKEY_USERS\.DEFAULT\Software\sleepnmojo\bob] Create a new user, and login. Which one does it use? Now prove me wrong.

I have pro, and my friend has home. When I go to work on his computer, it doesn't have any tools that are useful. It works fine for him, but if you are more advanced, and like to have more control over the OS, then I say go pro. As for resource usage, I haven't noticed a problem on either. I usually shut down a lot of unneeded services, so that might help.

I know what .default is, and it is not what you describe. You are confusing .default with the default user, like so many other people on this board. They are two very different things. There really needs to be a FAQ about this somewhere. I'm getting tired of seeing it everywhere. .default - login session, located at HKU\.default default user - located at %PATHTODOCSANDSETTINGS%\Default User (usually), needs to be loaded in order to edit. Please people for the love of God, please understand this. I talk about it more in this thread I would have assumed you were trying to do it via a reg file or inf. You could always try the full path to reg.exe to see if that works, but if you got it working, I don't see a point.

Why on earth are you looking in .default? Unless you care about the login screen having it on. You are looking for HKCU or HKU\crap you shouldn't care about. Like someone said, look for where you're grabbing the default user, and just modify it's registry. The reg key posted should work.

fastdetect I would most likely say no. You can always test it, and I would use a tool like bootvis to show startup values rather than what you "see". nodebug really isn't needed. Looks like its only real purpose is to disable the /debug parameter. This could be is you set up a parameter, and don't want to delete some other options that you put.

Another method returned from a search

You need to use upx to decompress it. upx.exe -d moo.sfx Then reshack the sfx file.

Yeah thats it, I'm glad some people know how to search. Thats the old version though. I put that in my cmd file to build my cd. The new one is like it, but just adds the registry keys, no extra file. I'll post it eventually.

I would bet your life on it. The only extras he has put in are useful ones. Yet none of those overwrote a Microsoft version of the file, unless by another Microsoft file. What you are asking is taking 3rd Party Software, and overwriting Microsoft software. I don't see that flying with RyanVM. His response would most likely be, "no". You could always ask him on his forum, and not in a completely unrelated topic.

I don't think you need to tell him how to do it. Why not use metapad, or notepad++? I don't think he will add a 3rd party program to the pack. If it is a MS program, I can see it making the list. Next thing you know, grandma will want her favorite game in the pack, and it will be huge. I'd say stick to putting it in yourself.

Back in the 9X days the programs were different. Now both programs are the same. Regedt32 is just a loader for regedit now. I'd stick with regedit.

could be either a problem with copying the files to the hd, or making the iso. My guess would be a bad copy. Open up the i386 folder, and look for usbheichi.sy_ or usbheichi.sys. Check to see if they are in the original, or sp2. If it isn't then something is editing a file that shouldn't be. Try taking out the /integrate of hotfixes step, and see if the problem goes away. Post your findings, and we can go from there.