Jump to content

Delprat

Member
  • Posts

    484
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    France

Everything posted by Delprat

  1. he said he don't have the .theme ebrahim, you'll need to create the .theme. It's a text file (like-ini syntax), and you can find some examples in the forums. The easiest way to create one is to set your .msstyle on your PC, set also sounds, colors, cursors in the control panels, then go back to display settings, first tab, and click "save as" --> there you'll get your .theme
  2. Delprat

    ICON?

    It's "undock laptop"... afaik, it's shown in the classic start menu with "close session" & "shutdown" (when the laptop is docked). btw, why did you post a HUGE screen capture ?????
  3. If i understand correctly, you want one install to copy this file, and another that don't (and you use two boot folders for that). But, in fact, you can *always* copy your RunOnce.cmd : one WINNT.SIF will lauch it, the other will ignore it. To do that : 1) optional step : MAKECAB RunOnce.cmd 2) copy RunOnce.cmd or RunOnce.cm_ in i386 3) add this line in the [files] section of DosNet.inf (always ".cmd" here, no ".cm_") : d1,RunOnce.cmd 4) add this line in the [sourceDisksFiles] section of TxtSetup.sif (always ".cmd" here, no ".cm_") : RunOnce.cmd = 1,,,,,,,1,0,0 That's all : your file will be copied to C:\WINDOWS (or %Windir%) (it's not possible afaik to copy it to the root) The drawback is that it will not be deleted in both cases : you should use a second CMD ("RunOnceBoth.CMD") that take care of the cleanup, and run it in both install modes. Of course, RunOnceBoth.cmd must not delete RunOnce.cmd before it ran it seems complicated... there must be an easier way ! ++
  4. Camarade_Tux : If the replaced file is modpe'ed, the setup will install it. That's enough for me, and i will not try to get errors only to discover that i should have modpe'ed a file in order to have no errors (if it works, then it works) Super-Magician : No information at all is better than bad, false or incomplete information. (cf "1984")
  5. Open your windows and look at the nature... When there is too much electricity in the air, the storm explodes, and then birds sings. I were only saying him how he can reach the peak level Well... /me is leaving this thread surreptitiously (<-- automated translation, sorry)
  6. Why bothering with replacing a file on HDD during late setup stages when you can replace the file in the source CD/DVD ??? SFC will not complain if the modded file checksum is set by modifype. Or i'm using a hacked windows since 2 1/2 years Did you (or someone else) tested to place a (modded) file in HFEXPERT\WIN\SYSTEM32\dllcache ? I beleive it would drive SFC mad ? I don't remember btw, your urls are wrong ! MSFN Unattended guide : replacing other modified files Fred Vorck's HFSLIP manual (but this one is the page about APPREPLACEMENT)
  7. Like ennemies during war ? hougtimo, set a password in the bios, and then tell your dad he should pay you each time he wants to use his PC, or let you do what you want with it... it may really work ! ++
  8. Remembering Professor Tim's Incredible Machine...
  9. Where did you get them ? I can't read your site !
  10. Super-Magician, you're wrong ! When using APPREPLACEMENT, the target file ("notepad.exe" here) is replaced in the i386 folder. The DLLCACHE feature is a part of SFC, and it's done during windows setup... with the files in i386 oioldman, you're wrong ! During a normal install (that is, without HFSLIP, attended or unattended), you would replace the original file yourself following these steps : ren notepad2.exe notepad.exe modifype notepad.exe -c makecab /D CompressionMemory=21 /D CompressionType=LZX notepad.exe del notepad.exe move /y notepad.ex_ X:\CDROOT\i386 It is exactly what is done during APPREPLACEMENT process (but the original file is not deleted). (there's no point using $OEM$ : it leaves the original notepad in place) /me is still looking for the msfn unattended guide and fred vork's hfslip manual
  11. did i saw a new test version or is it more misunderstanding ? btw, i have a remark about hfanswer... : is it of any use ? i moved all it (possible) content into SET ...=... line in the main script, then i deleted the instructions pages (including gnu, drivercomp and cat removal), and i censored (walls have eyes now !)... and now my hfslip is an unattended hfslip i think you could do the same in the DL : i mean replacing the ECHO'ed instructions by REM'ed ones, include the hfanswer content in SET lines (with REMs around) but leave censored empty. So the user will still need to read the instructions, but all will be in a single CMD. does this sounds good or bad to you ? PS: to be fully honest : in fact, i'm just tired to modify it each time... hopefully this is very fast with a merging tool
  12. Yes, updates lists are hardcoded inside XPDown.exe, so nobody can help him to update his software
  13. Its name is put your right hand on the mouse and click everywhere you can... just kidding there is some stickied posts...
  14. Delprat

    Stop it…

    Another solution would be to make HFSLIP "auto-scriptable", like "multiple AHTEST". I explain a bit further : HFSLIP displays a prompt asking you which section do you want to run (eg: MAKEISO), saves the input in a file, and displays the prompt again until a blank line is entered. Then, this file is processed, and each section is called one after another. (Obviously, this idea is based on nlite interface ) (And it's the "ultimate anti-id***-proof feature" ) The main benefit is that the saved input could be re-used easily with something like "TYPE MyOwnScript.txt | HFSLIP.CMD" ; or even with a test to see if the input is an existing file ; or ... PS: do not imagine i'm serious
  15. Delprat

    Stop it…

    I second that, since i've made one It's there : http://www.msfn.org/board/index.php?showtopic=70302 Nothing complicated : it only slipstream fonts (fonts gets installed like the original ones, with a custom registry hive, after a little "validity check" to get their names) The CMD is to be ran *before* HFSLIP.CMD (if in a separate file) ; or before :HFEXPERT (if some wants to insert it in HFSLIP.CMD)... There's nothing to do for making HFext, only one line at the beginning : IF EXIST HFEXT\*.CMD FOR %%i IN (HFEXT\*.CMD) DO CALL %%i I've seen some cleanup in the latest "test releases" : this makes it easier to customize... So what's the point ? HFSLIP could become a very powerful tool, with ability to make RyanVM-like addons (it's not as complicated as a diff =)... Thanks tommyp, you're on the right way : i've not see any error since monthes (but maybe i'm making a *too simple* disc ) edit: oh, i forgot CalmiraXP
  16. Delprat

    Stop it…

    Why not using CalmiraXP instead of HFSLIP ?
  17. no no no... it was in IE4, before Win98. (of course, there's no Win95 with IE4, only IE3) I've already answered in the second post of this thread There's no need for any "black arrow"
  18. Delprat

    Make cab

    Of course, but i'm lazier than you May i ask you what is the difference between : FOR %i IN (*) DO something with the file %i -and- FOR /F "DELIMS=" %%? IN ('DIR/B/A-D') DO something with the file %%? hidden files maybe ? ++ edit: thanks Yzöwl
  19. There's multiple ways to "run" INF files : in fact, INF only means "information", and what is done depends on what program reads it. The one Shark007 posted is to be parsed by update.exe (the "microsoft hotfix package installer") : to use that INF-format, you only need to have update.exe and update.inf in the same folder, and run update.exe. (but i know nothing about this syntax). "classical" INF files are parsed either by setupapi.dll (the default right click > install command on WinXP) or advpack.dll (the default right click > install command on Win9x), and only advpack.dll allows the use of RunPreSetupCommands (or RunPost...) 1/ copy-paste these lines in c:\test.inf : [version] signature=$Windows NT$ [DefaultInstall] RunPreSetupCommands=Test.RunPreSetupCommands [Test.RunPreSetupCommands] notepad.exe c:\test.inf 2/ Run this command : rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 c:\test.inf Nothing works ! 3/ Run this command : rundll32.exe advpack.dll,LaunchINFSection c:\test.inf You'll see the contents of c:\test.inf in notepad. I didn't test with a batch, but something like "cmd.exe /c ..." should work. ++ edit: credits for this trick goes to jdoe : see this post
  20. Hmmm... it looks like Windows 95 with Internet Explorer 4, doesn't it ? edit: may i precise it wasn't a question ? this trick is nearly *eleven years old* (ough !), it was first publicly avaiable with the first public beta of IE4 Another trick : hold the CTRL key when you click on a folder or on a drive to see its contents in a menu...
  21. Delprat

    Make cab

    put all your files in a single folder at the cmd prompt, use CD command to go in that folder use this to compress all files : FOR %i IN (*) DO MAKECAB /D CompressionMemory=21 %i (the part in italic enables the max compression level) you'll get all the compressed files mixed up with the originals, to move the cabbed ones to a folder, use the MOVE command : MOVE *.??_ X:\Path\to\Cabbed\files\*.* ++
  22. are you looking for that : winnt32.exe /noreboot at least, it copies the install files on hd.
  23. The AsRock K8S8X is on the supported hardware list of speedfan. Since it's detection features are not "mobo-based" but "sensor chip-based", i would bet that your mobo is also supported. If you read the help file, you'll find directions to correct your stats. Another solution is to ask asrock : most mobo manufacturers provide a tool to monitor their products on the drivers disk (it may be the reason why ScubaSteve did not find more tools on Google) ++
  24. You should use the STEALH and/or SPACE methods, not the COMPLETE/* ones. And you really should try Diskeeper. The problem with O&O COMPLETE/* methods is that all files are rearranged, and even a little 100kb word document changed yesterday can make O&O think that moving that 3-years-old 4.7Gb DVD image is a great idea to optimize performance. (not sure that's good english, i hope you understand) My experience shows me that Diskeeper will not do so stupid things (do not read : "diskeeper algo is clever") But you don't have bucks to waste is that (and that is great 'coz i hate tom cruise) ; so you'll keep O&O. If this inimitable noise is the only that makes you sleep, you should use the COMPLETE/* method you prefer. If not, the question is how this little fragmentation affects performance : do you really see any difference between a STEALTH defrag and a COMPLETE one ? ++
  25. ...but you can try each file one by one, and report your results here : there may be some 32-bits binaries hidden
×
×
  • Create New...