caps_buster

After some battling with the not working XP install without the scsi drive support (not finding any drives) I managed to win and observed this: - after the modifyPE was used on the sfc_os.dll file, no warning message anymore (good) - after reboot, everything is installing well, until come the networking. It progress to about 50, maybe 60% and then stop and wait there forever (well, I waited about 5 or 8 minutes, but it is clearly not working) Conclusion - the hack I did "blind" to the setupapi.dll file is NOT working at all. Using the originall hosts file it hang too, so it was NOT my hosts file (that is a good news also), but the hack. As far as the 90 90 90 90 90 8B FF 55 8B EC 8B 45 2C 33 C9 3B C1 string goes, Fred, it is NOT FOUND in the setupapi.dll file my Windows XP SP1.0a Czech use. Any help? The file is for everyone awailable there to look that the string is nonpresent: [Link removed.] (BTW, it looks way more like the Windows 2000 SP4 file, that string matches - except the position...) Help?

Help? What does the drives detection really need in the txtsetup.sif ...?

My first winnt.sif attempt: ...but with the "help" of my modified txtsetup.sif it cause a not working install. After loading and the black screen (just before the partition and formating job) it says that "no drives are found in machine" and install have to end, press F3 ... and reboot. What I did wrong? Where I overoptimized? txtsetup_caps_buster.zip

Excuse my lame question, but really all one need to do is to create a winnt.sif file (with abovementioned contents) and have it placed into the i386 directory and Windows install try (depending on the contents, of course) perform Unattended install? I was under the impression that the unattend.txt file is there for these purposes... edit: quick test prove me wrong, using unattend.txt did not mean anything to my WinXP SP 1.0a install, file is hapilly ignored...

Thank you, Fred, for your quite fast response. No, string "90 90 90 90 90 8B FF 55 8B EC 8B 45 2C 33 C9 3B C1" is not found in the Win XP SP1.0a version, at least not in the Czech one I'm about to try changing. You got PM with the file... And I tried different approach. Since W2k and XP are mostly the same, I tried searching for the "55 8B EC FF 75" sequance as with the Win2k SP4 setupapi.dll case. Quess what. Also FOUR instances of it, as in the W2k SP4 setupapi.dll file. So, as in the W2k, I blindly try to modify the second instance (as with W2k) - it is at 4F17D address and report back what happend when I try install WinXP with some modified files AND this modification of the setupapi.dll Brief preliminary report Failure - first it worked well, but at the end of the file copy phase, before the 1st reboot it complained that sfc_os.dll file is not winblows file, so for next try I have it modifyPE -c it and hopefully no messages anymore. After reboot everything seems to be good, but after the setups and CD key and so on it get to the network install. And there it just stop. The progress indicator is halted, the right down "working" indicator is moving, but that it is. CD detection work too, but it looks like that adding my 63kBy hosts file with blocked all M$ domains ( http://www.msfn.org/board/modifying-dnsapi...61.html&hl= ) is way too much for the network setup. Next try with standard hosts file. So, failure, tough both problems can be explained by other way and MAYBE the suggested modification of the setupapi.dll file for Windows 2000 SP4 on your site, Fred, is applicable to XP SP1.0a Windows. Just the address where to modify (witch of the strings, the second one...) is 4F17D - at least for Czech version of these XP Windows. Status - unconfirmed yet.

BTW, for the possibility of installing the already modified/different windows files, it is necessary to hack the setupapi.dll file (setupapi.dl_ in the i386 directory). Depecking (expand) it, hacking it, fixing the header (modifype setupapi.dll -c) and packing it with makecab again. Now there: http://www.vorck.com/windows/edit-setupapi.html Fred Vorck cover the need byte sequences for Windows 2000 SP4, Windows XP SP3 and Windows 2003 SP2. While all this is worth every penny and nice, I do miss the byte sequences/offsets for Windows XP SP 1 (or rather SP1.0a) and Windows XP SP2. Anyone know them?

The Linux drivers only have the very fortunate possibility of override the default settings by the "AllowNon60HzDFPModes" option that let the driver bypass the checks and allow any refreshrate to be set, and hence drive the TMDS to or even over it's limits. (I heard that it produce funny digital noise effects, if you go over it's capabilities, hehe) So basically it looks like that I have to search where the "60Hz refresh only on this chip" option of nVidia drivers is stored and then modify it (on installed drivers) and/or then go and modify the drivers to save the option as I want it - eg. leaving up to the user, how hard he want to drive his TMDS

Hi guys. I wonder if I can get some help when tweaking an old drivers for maximum performance and custom tweaks I already managed some tweaks that I describe bellow, yet still there is a pretty good deal of things that I simply don't know what to do with them, so a little help is need The drivers in question are oldie Forceware 45.28 ( http://rapidshare.com/files/290383806/Forceware_45.28.zip ) because they are VERY fast on the oldie computer (FX5600XT) and hence preffered. What I did accomplish nv4_disp.inf: %NVIDIA_NV31.DEV_0314.1% = nv4_NV3x, PCI\VEN_10DE&DEV_0314 NVIDIA_NV31.DEV_0314.1 = "NVIDIA GeForce FX 5600XT" (added these to make the drivers support FX 5600 XT card, otherwise no go - limitation, my card chip is reported as 5600SE, that had to be fixed in the nvcpl.dll by hand - replacing the 5600SE with 5600XT as it is in all later Forceware versions) nv4_disp.inf: [nv4.Services] AddService = nv, 0x00000002, nv4_Generic_Service_Inst, nv4_EventLog_Inst ;AddService = NVSvc, 0x00000000, nv_NVSVC_Inst (that disable the nVidia help service adding, it slow things down, lots of unnecessary HDD actions too...) nv4_disp.inf: [nv4.Services] AddService = nv, 0x00000002, nv4_Generic_Service_Inst ; nv4_EventLog_Inst (deleting the EventLog can only speed things up and I'm not a developer in need for logs, so...) nv4_disp.inf: HKR,, "DefaultSettings.XResolution",%REG_DWORD%,1280 HKR,, "DefaultSettings.YResolution",%REG_DWORD%,1024 (that give default resolution 1280x1024) nv4_disp.inf: In [nv4.SoftwareSettings] change AddReg = Default16BPP_AddReg to AddReg = Default32BPP_AddReg made, quite obviously, 32bits the default depth setup.iss: [File Transfer] OverwrittenReadOnly=NoToAll to: OverwrittenReadOnly=YesToAll (no questions on reinstall, I hope ) What I wonder about How to STOP creating many custom resolutions nVidia force us to have? First I cleaned out the modes.txt down to this for every card: 320 x 200 32 60 70 72 75 320 x 240 32 60 70 72 75 640 x 480 32 60 70 72 75 85 100 800 x 600 32 60 70 72 75 85 100 1024 x 768 32 60 70 72 75 85 100 1280 x 1024 32 60 70 72 75 85 100 and absolutely NOTHING in the "Horizontal Spanning Modes" and "Vertical Spanning Modes", yet with little change. Then I in nv4_disp.inf cleaned out these there lines: HKR,, NV_R&T + rest of the line HKR,, NV_Modes, %REG_MULTI_SZ% + rest of the line HKR,, NV_Modes, %REG_SZ_APPEND% + rest of the line down to this only ONE line: HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 320x200 320x240 640x480 800x600 1024x768 1280x1024" That worked out beautifully, yet still two resolutions I don't want are present. A 720x480 and 720x576. How to get rid of them? In the registers, they are not even there! That is driving me crazy. Do I need to hack some files? Let's hack them then! The BIG question. How to simulate the Linux option "AllowNon60HzDFPModes", witch I trying to find out unsucesfully. Looks like the TMDS encoder on my poor FX5600XT card wrongly fall into some category that says "60Hz only" in all Forceware drivers I tested (45.28, 53.03 WHQ, 81.95 WHQ)... I see two ways to get more that 60Hz. Okay, there. 1) modify the drivers somehow to disable the check, as the Linux option does 2) modify the BIOS in my FX5600XT to report more modern TMDS encoder, witch is allowed to use higher refreshrates over DVI 3) buy new GFX card - friend 7300GS with the very same monitor and some 75.xx Forceware drivers do 75Hz refresh w/o a glitch Yet since these card are not AGP and the FX5600XT got passive (nice quiet Zalman) cooling, the option no. 3 is not very viable one... Option two, modify the BIOS seems plausible, but after talking with NiBiTor autor Mavke it is on standstill now. He don't know where in the bios to look... As many of the TMDS encoders are in nVidia cards internal, it maybe even does not need to be in the BIOS. We simply don't know... If the TMDS are internal, then all you need to know is the GPU type and then you also know, if this TMDS is "locked" to 60Hz or unlocked. (according to the Linux users sucesfull attempts to get past this artificial barrier it seems logical that this is only artificial lock and not technical one - if my card can drive a 2048x1538 resolution in 60Hz, then 2,4x smaller number of pixels in 1280x1024 it sure can draw faster that in 60Hz - looks like it can do it at, 144Hz! ...but that could be wrong, of couse...) Okay, in fact, there is also option no. 4: use Linux, where things (probably) work! Oh, well. The Linux drivers only have the very fortunate possibility of override the default settings by the "AllowNon60HzDFPModes" option that let the driver bypass the checks and allow any refreshrate to be set, and hence drive the TMDS to or even over it's limits. (I heard that it produce funny digital noise effects, if you go over it's capabilities, heh) So basically it looks like that I have to search where the "60Hz refresh only on this chip" option of nVidia drivers is stored and then modify it (on installed drivers) and/or then go and modify the drivers to save the option as I want it - eg. leaving up to the user, how hard he want to drive his TMDS. Anyone know know and can help what anything there?

Okay, I replaced these lines in the [nv_SoftwareDeviceSettings] section of nv4_disp.inf file: HKR,, NV_Modes, %REG_MULTI_SZ%, ... HKR,, NV_Modes, %REG_SZ_APPEND%, ... HKR,, NV_Modes, %REG_SZ_APPEND%, ... HKR,, NV_Modes, %REG_SZ_APPEND%, ... HKR,, NV_Modes, %REG_SZ_APPEND%, ... ...with only this one with few default resolutions: HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 320x200 320x240 640x480 800x600 1024x768 1280x1024" And all other resolutions I did not wanted are gone, EXCEPT 720x480 and 720x576! Now that is weird, because these resolutions are nowhere near to be found even in the registry! ...now where are the 720 pix wide resolutions I wand to get rid off? Seek and destroy them!

This is VERY interesting thread indeed. Glen, good work, thanks! Did you tried to change/remove some of the added resolutions by the [nv_SoftwareDeviceSettings] - HKR,, NV_Modes, %REG_MULTI_SZ% and HKR,, NV_Modes, %REG_SZ_APPEND%, ...? I wonder if editing these lines let me get rid of many unwanted resolutions nVidia is forcing on my computer, like 720x480 720x576 848x480 1280x720 1280x768 1280x960 Anyone?

I believe you are mistaken. CDROM's did not get any much faster in past years and the install is hence still slow, when it need to load bunch of small files that are not need on 99% of machines. CPU power and amounts of ram does not help here. The only serious problem is the need for hacking the depacked setupapi.dll (expand setupapi.dl_ setupapi.dll) file and then apply modifype setupapi.dll -c and compress it again (makecab setupapi.dll setupapi.dl_) and then place in to your install CD. The change, when stripped down most of the useless things, is really like 50% faster. So, if you are like wasting your time while Windows setup is loading SCSI drivers for HW you haver even seen, then you are welcome to wait "faster" on faster machine Never mind. There are a ways to not reinstall too much. DríveImage (ImageCenter today) is the answer... Just backup the fresh install and you can change and add drivers/stuff w/o reinstalling.

Did fresh install to test recently and no change in behaviour Help?

What about disable WFP and use the dnsapi.dll from Win XP SP1.0a ...? I do worry especially about servers with HIGHLY suspicious names on the first sight, like: a00000000000000000000000000000000000000000000000000000000000001.ms.a.microsoft.com a00000000000000000000000000000000000000000000000000000000000002.ms.a.microsoft.com a00000000000000000000000000000000000000000000000000000000000003.ms.a.microsoft.com a000000000000000000000000000000000000000000000000000000000001.ms.a.microsoft.com a00000000000000000000000000000000000000000000000000000000001.ms.a.microsoft.com a00000000000000000000000000000000000000000000000000000000001337.ms.a.microsoft.com a0000000000000000000000000000000000000000000000000000000001.ms.a.microsoft.com a0000000000000000000000001.ms.a.microsoft.com a0000000000000000000000002.ms.a.microsoft.com a0000000000000000001.ms.a.microsoft.com a000000000000000003.ms.a.microsoft.com a000001.ms.a.microsoft.com a102.ms.a.microsoft.com And thanks to the xt guy, I include the compete M$ list. Added to my hosts files to prevent unwanted spying from M$. Enjoy! ms_hosts.zip

Interesting. Can I have the list of the M$ domains you choosed to block? Might be interesting in my Win2k SP4 too... thanks! As for the original question - tried checking out the reginst sections in regedit? Usually many weird stuff is hidden there, just check out this: http://www.msfn.org/board/index.php?showtopic=133333

Once I edit any font (mostly char mappings changes only), the font fail to render (just blank screen instead of font preview) untill the next reboot. So, is there a way to "reboot" the font(s) by rescanning/refresing their list or something like that?

Indexing service? I always disable it, because I do believe that it is used to index the NTFS HDD partitions to speed up searching, or so they say... And - granted. I start it, and no change in behaviour. You say this might depend on application? I'm affraid that I updated Firefox from 3.0.11 to 3.0.13 ...

I wonder who can tell me, on what is dependent the "filename autocompletion". I maybe name it wrong, but what I mean is that when for example uploading image on web pictures hosting, then before windows reinstall I only need to enter the image NAME, w/o the ".jpg" and it worked fine and the filename it completed by the comdlg32 dll that handle the open/save file requests. Now I probably overoptimized in Autoruns and disabled something that should not be disabled, I quess. Anyone have some hints about what can be re-enabled to get this "extension of filename automcompletion" working again? Thanks for suggestions

-X- - thanks! Unlocking these registry keys using the regedt32 worked jest great. They all had passed some properties that make then uneditable and so on, so removing this AND setting the permissions to "allow" for everyone and then deleting them fixed the annoying problem Thanks, great to know it is possible to lock some registry to prevent user changing it...

Well, first at all I tried the FlashUtil from 9.0b and yea! Much better, only two errors now: So far, so good. However using the Flash 10 utility by the same way ( -uninstallUnlock ) I get this error message: Something about impossibility of finding a "GetSystemWow64DirectoryA" is not possible in the kernel32.dll ... hmmm. So, I tried the other options of the FlashUtil9: -unregisterBroker -uninstallDelete -uninstallControlPath -uninstallBrokerPath -uninstallSafeVersions ...but with bad result, as the number of errors only increased by one Next try - I try unlocking these registry keys using the regedt32 Let's hope for the best

Are you sure regedit under windows 2000 SP4 has the ability to tweak permissions on registers? I never seen that and I quickly went into the regedit to check, but I did not see anything like it... And uninstalled, well... if I just download these flash installs again and unpack and use the FlashUtil - then it might work/help?

Hello, friends. On friend machine I made the mistake of installing the Adobe Macromedia Flash, instead of just depacking the installer and copy over the relevant files in Firefox plugins. As result, there are several non-deletable (regeditor refuse to delete them, CCleaner did not delete them as well) registry entries: Both from Flash 9b and 10b versions as you can see in the image. Since regedit refuse the delete the keys AND CCleaner also refuse to delete them, I tried even the Registry Booster, yet this one did not even list them as error. If that is significant, I don't know. I just want them to "go away" and don't know how. Thinking about Windows PE boot, but not sure if that is safe and if that will allow well me to manipulate with registry... Is not there any other way? There is NOTHING from the flash files in Windows directory at all. All are removed/deleted. I stick with the flashplayer.xpt NPSWF32.dll NPSWF32_FlashUtil.exe files extracted from the install and put in Firefox / Plugins, so I will not ever install that crap again. Never did on my machine and no problemo. But in case someone do, is there a known way to fix this? Using the Adobe utility to clean up is NOT the way to do... Also installing new version did not seems to fix a thing.

Good news. MicroAngelo did not break the order of icons, so... Good program! However I learn that the 16 colors icons must be ughly, becuase the 16 col VGA palete IS fixed, so... Anyway, I go for 256 colors icon then and - it worked right away! Now that is definitively MUCH nicer icon, hehe Another ughly bitmap is located in sysdm.cpl file - the my computer properties one. 16 colors, but as long as 13 color is 255,0,255 and not used (will become transparent color), a 256 colors BMP with RLE compression is accepted: Heheh Source penguin image is from there: http://snipp.hostuju.cz/linux.gif ... my version of the monitor is there: http://ax2.php5.cz/win_sys_bitmap_new.bmp and yes, I made the window a bit wider, so even the descriptions of LONG CPUs fit (AXP M come to my mind) there and the serial was shorted a lot to prevent others see too much :-) (another way is select not show in the properties of this text...) Enjoy!

If you actually try modify the user32.dll for yourself, you quickyl realize that altrought you can select individual icons and let the ResHacker replace them, it always end up with replacing the WHOLE group 105, witch is these start menu icons... If you have only ONE icon in the file, the there is a problem. Or if the icons have different depth (16colors) or different arrangement...

Well, the point is, that I did not want anything else (Daedalus), only change the icon And that could be the difference and why I must have 16 colors icon only. Because originally, W2k is pretty color-limited for these icons, so... No use for non Daedalus W2k. Only thing I need is to create the **** ico file the way it has to be done and THAT IT IS, I hope at least...

Kelsenellenelvian - Yep, that is exactly the issue. I can't produce the icon the way it need to be - 16 colors and ORGANIZED that way, M$ see fit. Witch is definitively NOT from the biggest size to the lowest, sadly. Articons suxx then, my friend tried to use icoFX 1.6 and same results. However he managed 16 color icons, as the original png bitmaps are, but they are drop-dead ughly, no idea why. Each icon can have different and own 16 color palete, right? And they are already 16 color ones, so... Tripo - now come on, you can't be serious. I was looking for ONE slight change and I already find it, just need the **** icon to be assembled they way it has to be, and you come with complete skin project? Oh my... That is not helpfull, mate. I have zero ambitions to convert my nice small Win2k into bloated (even in the form of excessive graphic) Win Vista. No way. Thanks, but no thanks. Colonel O'Neill - True, that is what I found too. However the Bitmat 107 is also ONE time used during start - when user prefs are loading and user is logging on. It is even on old slow computer a small fraction of second, but the "flick" is there and you notice it. Hence I have to recommend change both bitmaps. Yea, but that is useless. They have to be 16 colors (the png bitmaps already IS 16 colors) and sorted the way they is, eg. 32x32 10x10 14x14 12x12 16x16 22x22 256 or true color bitmaps are no-no for Win2k menu. Thanks for trying anyway. Yes, of course. 32 x 32 (16 colors) - Ordinal name: 1 10 x 10 (16 colors) - Ordinal name: 2 14 x 14 (16 colors) - Ordinal name: 3 12 x 12 (16 colors) - Ordinal name: 4 16 x 16 (16 colors) - Ordinal name: 5 22 x 22 (16 colors) - Ordinal name: 6