Delprat

maybe the /Q switch : DEL /F/S/Q %TEMP%\*.* If i were you, i would use the clean manager. run CLEANMGR /SAGESET:99 ; check what you want to delete, then run CLEANMGR /SAGERUN:99 each time you want to cleanup things. (you can have multiple schemes, just change the number) ++

Is this sentence scientifically proved ?Yes and no. Yes, the more people take the poll, the results will better represent the population (if people are being honest).That's how the effectiveness of medications are **proven**. (...) People testing medications are choosen (that is, they do not ask random persons at the corner like in this poll, or like in the elections). And once a test was made, it is made again. As time goes with more and more different medicaments, we see more and more evidences of ineffective ones... You misunderstood my previous post : more people doesn't mean more representative. You're true about the 'original intentions', but you did colored your sentence as if it were always true. And obviously, MSFN members are not representative of hard drives users, thus more answers will not allow a better extrapolation... Anyway, to know the reliability of a hard drive, there is something called MTBF, computed in a way used day by day, and most probably representative (more than the poll for sure : imagine that protocols used for MTBF are also used before allowing a car, a truck or a plane to be used...) ++

I'm too having a problem to understand... Look if i'm correct : Most operating systems (including windows) does never delete the file's data from the disk, they only clear the allocation tables, so it's always possible to retrieve the data unless something else was written on it. (yes, you need external tools) Internet Explorer data (cache, cookies, history) are normal files (if seen from the OS), and can be restored the same way (except IE relies on "index.dat" files that gets overwritten, so restored files can not be seen by IE). Network files... i'm not sure what you're labelling so. It works like for floppies (or remote device), files don't go to a "recycle bin" but data is not overwritten. I don't know what is an "average" person (average relies on what is your office), but i would say you're true and your managers are bloody curious... ++

It's at least eight times 20MB (when using NTFS compression on the various folders), plus A LOT, A HUGE LOT of registry data that loads in memory everytime... (so many reg crap that the installer takes more time bloating the registry than installing files...) And MS just released a patch for .net 2... wait ! a patch ? So there were something bad in .net ? And one can browse the net with a 1.44 MB operating system (QNX)...

What packs did you see ??? AFAICT : Booogy's WUZero Pack(s) contains all hotfixes released on WindowsUpdate RyanVM's Update Pack is the same plus non-public hotfixes, and a few more things (safedisc driver, makecab,...) Regarding these two, the second is closer to a pre-SP3, but can contain hotfixes you don't need (look at the changelogs, both authors had listed each included KBxxxxxx with the fixes' descriptions) ++

Is this sentence scientifically proved ? I were thinking of something like the monkeys typing randomly on typewriters. They have a chance (very little) to type an already existing novel. Same thing for polls : you can imagine that you asked *only* not-representative people, even if you ask more than three hundreds millions : it is exactly what happened when GWBush was elected the first time (only a few citizens of Miami District made the difference, making the entire country unrepresentative a posteriori) And this example is definately not an exception... ++ PS: When i posted, i made a mistake : the drive i believed to be a Seagate is in fact a Samsung.

Unfortunately, this example will not work. (i bet £10 you knew that ) One working way is to defer this loop in a batch. Another working way is to use nlite or hfslip to slipstream the hotfixes. Or use an update pack with nlite, hfslip or rvmintegrator. One untested way is to use something like that : [setupHotfixesToRun] C:\WINDOWS\SYSTEM32\CMD.EXE /E:ON /C @FOR %c 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 %c:\WIN51 SET CDROM=%c:)&@FOR %h IN (!CDROM!\I386\HOTFIXES\KB*.EXE) DO @(START /MIN /LOW /WAIT %h /Z /Q /O /N) That's on one single line. I used the full path to CMD 'coz i beleive environment variables (%windir% or %systemroot%) are not usable there. Good luck :clover: ++

bledd, i understood what newsposter said. > 2003 only maybe not at all ! beeps are made by a regular BIOS interrupt, and all operating systems are able to do it. Like i said, "soundcard" and "beeps" are not related, thus it beeps even inside a game or any app that gets exclusive soundcard access. (i'm sorry to have used "sound notification" in my previous post, i should have said "audible notification" to avoid confusion) On the other hand, there is no way (except rewriting beep.drv) to get beeps on the soundcard (because beep.drv has nothing to do with sound drivers) When i said « I dunno what you call "system beeps" », that were because of the existence of a sound event named "system beep" in windows sound schemes, making more confusion (obviously, this "system beep" is not a beep, it is a sound) Now it is time to replace "beep" by "bip" ++

DPC = Deferred Procedure Call http://www.sysinternals.com/information/advanceddpcs.html It can also be "Dead PC", or anything you taste Anyway, if one copies DPCDLL.DLL, PIDGEN.DLL, SETUPP.INI, OEMBIOS.* and some others (LOL) from one disk to another, he can use the key of the first disk on the second one. This is on the "things not to do to stay legit" list ! ++

well, to get a submenu like winrar, you need to code something called a "shell extension" (you can't have submenues with reg settings AFAICT). Here's a tutorial : http://www.codeproject.com/shell/shellextguideindex.asp It doesn't cover the "submenu" part, but if you understand the rest of it, the submenu will be easy to add. There is easier/faster methods, one is to use the classic "sendto" menu, another is to use a pre-made shell extension called "CMenu" (search on MSFN, there's a thread about it). Main disadvantage is you'll get your entries for *all* filetypes. To get the directory of "%1", you need to call a batch, and inside this batch use something like : your-program.exe -src-dir="%~p1" -src-name-without-ext="%~n1" -src-ext="%~x1" -src-drive="%~d1" -src-full-path="%~dp1" -src-name-plus-ext="%~nx1" -src-short-full-path-with-name-plus-ext="%~sdpnx1" -out-dir="C:\out" -evenmoreswithches See the FOR /? last help page for more info on this. (i'd bet it would be possible to use %~... in the registry by calling cmd.exe /e:on /c @for %i in (%1) do @your-program.exe -src-dir="%~pi"... but i never tried) ++

Why not just unplugging the beeper from your mainboard ? Anyway... this driver is very useful to receive sound notifications during a game getting exclusive access to soundcard (ex. for IM, mail, monitoring tools, IP phone, ....) I dunno what you call "system beeps", but the soundcards will never play any "beep". ++

No one but an IA can have discovered this : an human would never have tried such a file ++

"best link" ??? what if one wants anything but an erotic wall ?

i don't know who made this, but he(*) made an enormous mistake(?) in the title : "fiancés". It's a french word reffering either to engaged *men*, or to one man and one woman. The author should have used "fiancées" if he (*) wanted to refer to engaged women. (*): but maybe a woman made this, who knows ? ++

This is not MSGINA but LOGONUI. The blue box is by default the windows logo (the flag plus "Microsft Windows") visible also during bootup, on the logon screen, and during logon. The message "Windows is shutting down" is part of the normal status messages. If you want to see the extended ones, you need to use "classic logon" (without LOGONUI) ++

One working WD 80 GB 6 years old One working WD 80 GB 5 years old One working Seagate 10 GB 8 years old One working Maxtor 1.2 GB 10+ years old One working Maxtor ~500 MB 10+ years old (bought with a 486 DX) One working Maxtor ~320 MB 10+ years old, maybe 15 ? (bought with a 386 SX, but i'm not sure it was a Maxtor in fact) (the last one has about 10% bad sectors after a power failure -- i guess the heads has landed !) AFAIK, these 3 brands are equivalent in terms of quality if seen on the long term. But some models are better than others. If you want a reliable drive, look for "special edition" ones (sometimes they have twice cache, sometimes a better case, etc...) ++

You don't need a so powerful hammer to break an egg ! Driver binaries should go in CAB files referenced in drvindex.inf (also contains the list of included files), txtsetup.sif & dosnet.inf. You can have as many different CABs as you need (by default, there is driver.cab, sp1.cab, sp2.cab, etc...). Then these CABs should get copied to %systemroot%\Driver Cache\i386... In theory, windows will find the binaries correctly (except if the .inf uses a tag file) ++

(bump) Sounds like a bad solution to me. Sometimes you will have a case where you don't want to answer the same to all boxes, and you'll run into problems because you don't know which files collides before selecting "yes/no to all". A very good solution would be to display a summary box with all file collisions. That's not possible actually since each hotfix/addon is parsed after the previous one, but having one summary box for each is feasible (this box should let the user select each file individually). ++ PS: not related, but if even nuhi comes to this thread : why on hell, when a CD is selected as source, nlites copies the whole ~550MB to HD before asking the user if he wants to delete 300 MB of these ? why on hell driver.cab & sp*.cab is first copied to HD then extracted instead of extracting from CD to HD ?

I don't understand what you're trying to do : you check if the driver is installed before installing it ??? Anyway, to have a runonceex on second reboot, you need to add a runonceex entry that will add a runonceex entry. An example to make thing clear : IF EXIST %systemroot%\system32\drivers\ctaud2k.sys ( REG ADD %KEY%\002 /VE /D "Preparing to Install Audigy 2ZS driver on next reboot" /f REG ADD %KEY%\002 /V 1 /D "REG ADD %KEY%\002 /VE /D ""Installing Audigy 2ZS driver"" /f" /f REG ADD %KEY%\002 /V 1 /D "REG ADD %KEY%\002 /V 1 /D ""%CDROM%\SOFTWARE\Drivers\SB\Audio\Setup\setup.exe -s"" /f" /f ) (or you can have a separate batch called from first-boot-runonceex that adds the second-boot-runonceex entries : it's easier to work on) ++

I use this : http://www.msfn.org/board/index.php?showto...7584&st=8#9 (look also for the full topic if you prefer a drag-n-drop thing) ++

Camarade_Tux, "foobar" is not an encoder. This tread is about foobar2000, which is mostly an audio player (even if it can encode audio files or do DAE of cds, it relies on external plugins). "foobar" is a word used to mean "whatever you want", like in « create two nested and two parallel folders using mkdir command once : mkdir foobar foo\bar ». The short for "foobar2000" is "fb2k" and NEVER "foobar", even if it's a very common mistake (strangely "fb2k" is shorter than "foobar"). Like for that "intelligent car" old(ish) tv-serie, K2000 : you could say "K2K" and it would make sense, but saying just "K" will make everyone think about MIB. monohouse : my HD is the third of that... but i have multiple versions of songs (mainly different interprets) for example and it's handy to get them all by typing the title once. or sometimes i want to get "all songs with lyrics by X". I acheive this with the extended playlist generator on 0.8.3, and i bet the "autoplaylists" of 0.9 would be even easier to use. but i don't want to spend the required time to update my config (lots of formatting made to get correct display of some tags...). That's nearly impossible to sort all of that using directories, because there is not one hierarchy. My files follows a simple "Genre - Artist - Album" structure on the disk, but this doesn't allow easy navigation for the two queries i talked about : the library get rid of these limits by creating a database which support multidimensional queries (like "i want song by the same interpret as the playing one but with lyrics by X. i know i have plenty, but i don't remember all of them by heart" or "i have added two albums on my drive a week ago, i never heard them, i don't even know the titles, but i want them know and i don't want to search" ) I use fb2k because it's light (even with more than 3 plugins), and because it has an "easy-to-forget" interface (exact opposite than winamp's complicated UI with things hidden at every corner : with fb2k, i placed all i need in the context menu, not more, not less). I don't understand your p.o.v. about the difference between an "audio player" and an "audio converter". If i have the file under my eye, and if i want to convert it, i don't want to launch a secondary app if i could not... CLI acheive this by launching the external converter. ++

you're true, last time i went on HA.org KS playing mode were not ported to 0.9. i didn't checked .1 nor .2 I'm nor an audiophile, but : -> i need a library thing. i have tons of music, and it's very well organized, but it's always faster to type in a little keyword than clicking several times to browse folders. -> the diskwriter contains CLI components to call externals converters. it's meant to have all under a single UI -> you should post the rest of your suggestions on HA.org (keep in mind that fb2k is "plugin-driven" and that most of the new gadgets you dislike are easy to wipe out) ++

Help yourself by learning How To Ask Questions The Smart Way. ++

Nothing is centralized. Avoid headaches and go on with the batch idea. Or look at sysoc.inf & syssetup.inf(*), then in all *.inf referenced in these two. But this will not work for all shorcuts (ex: IE & OE & WMP shortcuts are created by an exe) ++ (*) syssetup.inf creates some shortcuts, but it's not possible to modify it without hacking syssetup.dll AFAIK

Many things were rewritten, i don't remember all, but there is for example a better support of APE tags in MPC files (they were really slow to update on 0.8.3) ; the "database" is now named "media library" (and is not compatible) ; there's the diskwriter also... and so on... but i'm with you about the 0.8.3... i'll wait for 1.0 ! ++