Jump to content

Delprat

Member
  • Posts

    484
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    France

Everything posted by Delprat

  1. Quote from Winpooch.com : This is a powerful method under 9x systems, but AFAICT, under NT, drivers can be ran at a lower level (like file system filters) and then fool Winpooch. My advice : do not trust Winpooch if you're not planning to use it on a 100% clean system. btw, very nice graphics. PS: the first URL link on free.fr is 404 ++ edit: my advice was about installing it on a clean system. sorry.
  2. This is no more than a graphical restriction (same as TweakUI) : you will still be able to access the drive simply by typing its driveletter (in the explorer address bar, is the run box, in the open/save dialogs, in the command line box, etc...) And even if the computer has no keyboard, there's still copy/pasting... Avoid this trick, it's outdated (as old as win95) ++
  3. 'lo, First of all, MS did released a toy labelled "Microsoft Private Folder" or something like. It allow you to set a password protection to any folder. (but i guess this protection is not very strong) Then, you can use NTFS built-in security permissions (ACLs). You need either XP Pro, or XP Home in safe mode to access these settings : right-click on a folder you own, select properties and in the "Security" tab you can adjust who is allowed or not to read, view, etc, any file. You have two boxes, the top one list all users/groups that have some access granted or denied, and the bottom list are the actual permissions. If you want to deny anyone to access a file except you, you just have to remove anyone except you from the top list, then add the built-in group "Everyone" in the top box and deny this group all accesses. This would work if you are the owner of the file/folder, something you can manage in the advanded box, which also holds inheritance settings useful when you manage a folder. Take also note that an administrator will always be able to take ownership of your file/folder and modify the permissions you set. ++
  4. Delprat

    <DELETED>

    911cd.net ? thanks god, you're on FAT... +
  5. could you translate in plain english (or other modern language) ? about 7-zip, instead of that so old meaningless switches try the standard NSIS switch : "/S" (capital letter) (and this info is present in FAQs at 7z.org & here) ++
  6. DVD drives are costing so much these days that buying two drives (one for each region) and stay legit is far from a PITA. Of course i'm talking of DVD drives *for computer*... but is this practice really legit ? ++
  7. unattended> what you wrote is true for the "defaulthide" & "providedefaults" modes. you should either fill in all the (required) fields, or if you're adventurous select "fullunattended" and setup will not show anything (but will fail if critical settings are missing, like user name, etc) repair > yes, repairinstall is disabled if there is an answer file. and repair install is not unattended (it asks for the key, allowing you to "repair" with a different edition). if you want, before making the iso in nlite, take winnt.sif out of the i386 dir and place it on a floppy, then you will be able to do normal/repair installs with the CD, and you will still be able to do unattended installs by inserting the floppy (this method is really powerful : you can easily have multiple answer files on the same floppy, and rename the good one to "winnt.sif" before installing any WinNT 5 OSes : 2000, xp, 2003) recovery (console) > has nothing to do with repair install, so i'm not sure you were talking about that(*). anyway, to install it just add "winnt32 /cmdcons /unattend" in the commands to run during setup (or hit F10 when you're prompted to hit F6 at the very beginning of the textmode setup) sfc.exe > it's related to WFP... do not hack it, and do not remove protected files if you want to run it flawlessly... (or at least, use the CD corresponding to the current install, in other words, a disc with the same things in : i doubt you can have a "minimal" disc to sfc-ize a "full" OS) ++ edit: (*) seeing back the thread title, i'm sure of the opposite now
  8. Only videos that really require Windows Media are videos in Windows Media Video format (same goes for sounds : WM Audio). If you do the correct file associations with <insert here the name of your favorite player>, you shouldn't need WMP, except for streaming maybe ? ++
  9. i had have similar problem, and it was before i ever tried Xpize. It was caused by a corrupt uxtheme.dll (so the "themes" service didn't started), badly patched by a "multi patcher" that wasn't aware of the good build number. ++
  10. 256 colors graphics are the only true graphics. (any good coder would say it ! true color graphics can't do palette rotations ) Hey, remember Win 3.1, the boot logo was only 16 colors, and there was already some linux fans to say "if your linux kernel support it, you can have 256 colors boot logos !". gr8t ! And once people get 2^3456 colors on their boot screen, they will get stuck in a "rebooting computer" loop to watch the boot logo, and never work /my two cents ++
  11. mate, xmouse settings in tweakui are the answer ++
  12. The PSU on the picture is not, or i need glasses. And about that carpet ? ++
  13. many things can't be... i use mainly FF, but it starts in tenth of seconds when IE appears in less than 2. FF uses a lot more memory (now : 85 megs with one single tab and one single window !!! there are whole OSes of the tenth of this size that include browsers !!!) FF doesn't support embedding of HTML applications (HTA) nor OLE (ex: word inside IE) some websites works bettter in IE FF bookmarks are not shown in start menu FF can't create MHT (which are very handy... there's an extension that allow similar thing, but IIRC that's still not MHT readable by 99% of windowes) and lots more... ++
  14. and a third one. no need for VLC if playing DVDs is the objective. (just compare the sizes ) + + edit: i do not "play" the menues
  15. answer is dual : A. it does not because on your harddriv, files compressed are packed with ntfs compression, which is not "manageable" (no "min" nor "max" setting : it's just packed or not)) but A. it does because diver.cab is copied on the harddrive, a smaller one on CD obviously means a smaller one on harddrive. ++
  16. That's a fake picture, as proven by the carpet. And there's not enough room for the PSU unless it's as small as an optical drive.
  17. I can reproduce your "bug" by installing XP on the same partition that an existing XP installation, with identic "Documents & Settings" folder, and optionally with different system and/or programfiles folders. AFAIK, this tagging of the profiles's folders is made to allow this sort of concurrent installs to run with the same "D&S" folder containing profiles with the same screenname, but different on drive. My guess is that your $oem$ thing is copying files to X:\Documents & Settings\Administrator that XP setup recognize as "oops there's an old profile here i need to use another folder" (maybe ntuser.dat ? i really don't know if this guess is even possible ???) About your scripts, you just shouldn't be using an hardcoded profile folder name ; instead, you can retrieve it from the registry : HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList contains a subkey for each profile (and special values for All Users and Default User, just look), whose name is the user's SID. You can easily catch the admin profile by checking if the key name ends with "-500", then read the ProfileImagePath value to know the local folder name. ++
  18. if i understood corectly, you're trying to create URL shortcuts with a target field containg an URI built on the form "file:%Var%" ????? Just create LNK shortcut with your %Var% in the target field. Alternatively, you can create a LNK shortcut to a local batch file that will create an URL shortcut containing the expanded value of %Var%. You can also go from New York to Chicago via Los Angeles, but that's really a long way... if i didn't understood correctly, good luck ++ Post edited. Don't insult other members. --Zxian
  19. straytoasters, if the /integrate switch logic you described doesn't makes you happy, you can just rename the downloaded EXE packages to someting in 8.3 (that is KB123456.EXE and like), and create the svcpack.inf yourself (probably with /passive /o /n /z, or /q /o /n /z). The guide unattended.msfn.org explains that somewhere. Takeshi, please read (more carefully) the link you posted before saying such things. Without /passive, /integrate shows a dialog "integration successfull" (or like) and waits for a click. [offtopic]And i'm very interested in an explanaion of that "thing"(?) in the From: field of your profile ?[/offtopic] ++
  20. First, you'll need to have the two TTF files in <windows folder>\fonts before first reboot. Three solutions : A (beginner level)> copy SegoeUI.ttf and SegoeUIBold.ttf in $oem$\$$\fonts, and be sure to have OemPreinstall=Yes in winnt.sif B (i hate cows level)> copy SegoeUI.ttf to I386, cab it, copy SegoeUIBold.ttf to I386, rename to SegoeUIB.ttf and cab it. Then add the two files in DosNet.inf, and in TxtSetUP.sif (renaming back SegoeUIB.ttf to SegoeUIBold.ttf via txtsetup.sif) C (i format my hd every two hours level)> use a pyron's modded setup.exe, and a custom presetup.cmd to copy the .ttf files Second, to register the fonts you need to add a line for each in your hives' AddReg sections : HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","Segoe UI (TrueType)",0x00000000,"SegoeUI.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","Segoe UI Bold (TrueType)",0x00000000,"SegoeUIBold.ttf" (HIVESYS.INF and HIVESFT.INF are the best choices IMHO) ++
  21. http://www.lunaelement.net/ -or- Luna Royale by Pgase ++
  22. If the mobo is of the same architecture, you should be able to boot into safe mode, then install the new drivers from there. ++
  23. hmmm... this is a well spread guide since *ages* (at least a decade) I don't want to be unpolite, but why on hell one should just follow step 2 ? IMO, step 1 is correct, but step 2 should just read "use it" because the adventurous user that follows step 2 of your guide can get into BIG troubles (no joking). About the other tweaks suggested/discussed here... seems strange no one is posting his own benchmarks ?!?!? come on people, all these theories are pointless only benchmark i saw here (but i may have read too fast) is bootvis on majorgeeks (a tool intended to debug driver loading delays, in other words, a tool for driver developpers...)... hey, i've got a better solution : just use hibernation feature not only it's faster, but it's also allowing you to keep, say, a firefox or IE session opened, or Word, or OO.org, or even some games (depending on the quality of the drivers on your system)... okay, now if one using a decent computer(less than 5 years) can show everyone a list of tweaks that improve perfs for human eyes (for example : all delays between 10-40 sec are to be seen as "identical or nearly", all longer are "too long", and all shorter are "good scores"), i'm very interested... and with only tweaks that do not modify any of windows functionnalities ++
  24. you can probably succeed by using windows built-in tools. either START /B command (i never tested that) : [commands] ... c:\windows\system32\cmd.exe /k start /wait /b x:\path_to\your_batch.cmd or a VBS/JS launcher ; search on the forum for details, but it's something like that : WScriptObject.Run("x:\path_to\your_batch.cmd",1,False) (the 1 "equals" /wait ; and the False means hidden ; or it's maybe the opposite, i still don't know the manual by heart ) ++
  25. 9l is the directx9 release for vista (for better backwards compatability with Dx9 games) it isn't for XP at all Yes, i saw. Please let me re-word my words (i'm unsure you understood) : I highly doubt that dx9L (the "brand new specially optimized directX"), under Vista (two words i omitted because it seems obvious that a software designed to run only under Vista will be run only under Vista), can run dx9 games (here, dx9, without the "L", is to be taken in its general meaning of "Win32 games using DX9 API") faster/better on the same hardware than a "normal" dx9 under XP... In short, take a computer, install XP+dx9, benchmark a dx9 game. (thus the hardware should fully support dx9 features, but no more). Then install Vista+dx9L on the same computer, and bechmark the same game. And i highly doubt that the second run will be faster/better than the first one. You can label these doubts "better backwards compatability". I'm waiting the final releases of all this stuff to see if "L" means "Lighthened" or "Lowered" or "Looser" or "nothing" (sh*t, no L here ) ++


×
×
  • Create New...