Quisquose

Thank you so much JFX. I would have never figured that out for myself.

Apologies for this dumb question. I'm trying to use 7Customer (which requires ImageX, Oscdimg and Dism). I used GetWaikTools to download the Win7 WAIK files and I can see ImageX and Oscdimg, but I cannot find Dism anywhere. Is GetWaikTools meant to obtain Dism as well?

Cleaning up the New list is all well and good, but it doesn't stop retards like Adobe programmers from arrogantly hard-coding forced shellnew creation every time their programs are run.

I just wanted to say a huge Thank You! to win2000 for his hard work creating this program and his generosity in sharing it with us. The problem of developers making their software XP only (when it's perfectly capable of running on Windows 2000) was becoming an increasing annoyance for me. It seems even small shareware programs are now starting to prevent Windows 2000 capability for no good reason at all. A couple of months ago I heard about an API wrapper that was created for fixing gaming applications (but which supposedly also worked 'sometimes' for non-gaming apps too). By the time I got round to trying to download this API wrapper, the link was broken and the web site domain was no longer registered (http://win2kgaming.siteburg.com/phpBB2/viewtopic.php?t=7). So I tried to search for alternative download links and that's when, by accident, I found KDW! From what I can see, KDW is an even better solution than the one that I was originally looking for. I have to admit that when I first looked at the KDW web site (and the instructions in this thread) I was really daunted by how complicated the whole process seemed to be, but having now got the hang of it, it's really not been that difficult so far. I just think the instructions are worded a bit confusingly because they're written by someone for whom English is not their native language and all the options shown at once on fcwin2k.exe is a bit scary. Anyway, I have managed to patch a couple of XP only MSI installers (which allowed the software to work just fine without any further adjustment). There was a third program (Camtasia Studio) that installed fine after the MSI patch, but the executables would not run. So I patched the executables too and now all 6 applications run perfectly (and all it took was 2 button clicks!). KDW has been a real life saver seeing as more and more software is needlessly being released in XP/Vista only format, so I just wanted to show my appreciation to win2000 for providing such a great fix for this problem.

It seems that the idiots at Creative have decided not to provide any Windows 2000 drivers for any of their current webcam range. I thought the whole point of WDM was so that one driver could be created and it would work on multiple Windows versions, so I don't know why Creative have gone out of their way to make a driver that is XP only. I notice that some webcams are supposedly driverless (i.e. USB Video Class) but this requires support in the OS. Is there a USB Video Class driver set that will work with Windows 2000?, or failing that can a regular XP webcam driver be hacked somehow to work on Windows 2000? I tried doing an inf install using the drivers that were supplied, but they were not recognised as compatible with the device.

I have an IcyDock MB-664US-1S external hard drive enclosure attached to the back eSATA port of an Asus P5W-DH motherboard. I boot two different OS's from my PC's internal drives (which attached using regular SATA). One OS is Windows 2000 (USP 5.1) and the other is Linux Mint (4.0 Daryna). I've noticed that whenever I click the shutdown icon in Linux mint, the external IcyDock enclosure powers down when the PC switches off, however when doing the equivalent from Windows 2000, the PC powers off but the IcyDock enclosure remains powered and running indefinitely. Does any one know why one OS should result in the external enclosure powering down while the other doesn't? I am at a total loss to even know where to start looking for an answer to this? Any advice gratefully received. Thanks.

Just out of interest, why do you prefer that method over others? I'd be interested to know because I am unfamiliar with the pros and cons of the different methods.

I've just tried a couple more of the extensions (I'm loving the check mark on the new Hidden Files Toggle menu, by the way) but these recent additions have also gone to the bottom of my context menu! I installed the Select All item last, but strangely it went into the second-to-last position rather than at the very bottom like previous two extensions did. Is there a means by which the Registry determines where to insert an item into the context menu?

I've just tested out these excellent shell extensions on my Win2k setup. They work fine, but the Sub-menu pack menu item appears at the very bottom of my context menu (below 'Properties') rather than in the position shown in the screenshot on the first post of this thread. Is there any way to fix this, or manually reposition the menu entry? Thanks.

If the newbie that I was helping was capable of installing a VNC server, configuring whatever ports / firewall rules are needed and then using a totally new interface, then I doubt that I'd need to be offering remote help to them in the first place. Netmeeting is very familiar to this person, the configuration is a simple wizard and so this would be the easiest option (if Microsoft just made the dàmn file available).

Does anyone have a copy of the above hotfix file? (Netmeeting-kb927853-x86-enu.msi) I use Windows 2000 and I am trying to offer some remote assistance to a friend who is not using Vista. In the past we just used NetMeeting to share the desktop so that I could fix problems remotely, but NetMeeting does not run on Vista, and whatever crap they've replaced NetMeeing with in Vista will not run on Windows 2000. I've seen on the Microsoft support site that there is a hotfix available that allows NetMeeting to work on Vista. Basically the hotfix is just NetMeeting v3.02 (i.e. version 3.01 patched to run on Vista) however, v3.02 allows the desktop to be shared on Vista (which won't work if you try to force a hack with v3.01). Microsoft (in their infinite stupidity ... as usual) have made this process as awkward as they possibly can by not making the hotfix available for download. You have to telephone them to get it. The Hotfix Share web site is the only other place that I can see where it can be downloaded http://thehotfixshare.net/board/index.php?automodule=downloads&showfile=463 but the stupid site will not send out an email to allow me to register. I've tried to register 3 times with different usernames and different email addresses, but no email gets dispatched to me. So, if anyone has a copy of the file itself (or if they have a Hotfix Share account that they could use to download the file) then I'd be most grateful. I hope someone can help. Thanks

And what do Windows 2000 users do?

Thanks for creating this great program! I love the concept of it (it's very useful) however it doesn't quite work for me. The program loads fine and the scroll lock lights up when mouse is over appropriate tray icon, however I can still get access to the context menu if I right click 3 or 4 times in a row. The first couple of times it doesn't work, but if you click another one or two times more then the menu will appear. Does this only happen on my system?

I had the same problem when I was trying XP64 a while ago. I mentioned it to Nuhi and asked if NLite could have an additional box for specifying x86 path separately. Nuhi said that it was not a bad idea, but that I was the very first person to suggest this. I made the suggestion to him back in December last year, so I guess not many people requested that particular feature if he has still not added it 10 months later.

I'm using ATI v7.2 drivers on Windows 2000 (unofficial SP5) with my Radeon X1950 Pro. I've tried the drivers both with the dot net Catalyst Control Centre (CCC) and with the Catalyst Control Panel (CCP - the old style tab add-ons to Display Properties) and both of them work fine.

Is it possible to edit the install paths in an MSI installer without having a full developer's IDE? I'd like to change the default install path to a location of my choosing. I can't fix the paths in the Registry after a default install because there are some keys created in HKLM that can not be edited because they are 'in use' and locked. Also, one of my MSI files (Microsoft PowerPoint Viewer) does not give me a choice of where to install it when manually setting it up (unlike the viewers for Word and Excel which do give you a browse dialog to choose your location). The PowerPoint viewer also does not respond to unattended install switches, so I'd like to fix this issue at the same time that I specify the default path.

I've tried that and it's hit and miss, sometimes it works ok and other times it doesn't (dxdiag shows DX v7.0 and 3d tests will not run). Also, installing DX at runonce ex really slows down the install process. Plus, DX has to be in place for certain other items to install, so if DX is not installed until the first log in, then those other driver packs that I could have sliptreamed won't work (they will have to also be installed later on after the DX install has completed). The result is that the Direct X Runonceex setup process always stalls because you get a load of "new hardware detected" wizards popping up ask for the location of drivers (because they have not been slipstreamed) and this prevents the DX install from completing because the wizards grab focus. It's all a bit of a mess really. Nlite works so simply for everything else (service packs, hotfixes, dotnet, AHCI text mode drivers etc) that I wonder why it has such a problem with Direct X. I can't understand why I can't just point Nlite to the DX files and have it slipstream it correctly (seeing as that works for all other cab packs).

Same here, and I am using ATI (Radeon X1950 Pro). Outpost tray icon is wrecked (as are Nero install icons) and I have folders of XP icons that all have very jagged black edges. Strangely, a couple of icons in the control panel seem to be displaying correctly, but I may be mistaken as I can't be sure how they looked before (I did not pay them that much attention). I have cleared icon cache, unregistered DLL and re-registered, but it's still the same unfortunately.

Hulkviper said "attach" your last session, not paste the whole dạmn thing into your message. It's no wonder people don't bother to search on these forums. You can't find any information on here because every word that you search on just brings up hundreds of threads of people's sessions (that have nothing to do with what you're looking for).

Has anyone been able to slipstream Realtek HD Audio drivers into their Windows install CDs? Mine won't work no matter what I do. I suspect in my case it may be down to a DirectX problem. After all my trials in this thread (LINK) I still can't get DirectX to work properly, and Realtek's readme states that it will not install without at least DirectX v8.1 being present. As I'm working on my Windows 2000 CD (which only has DX v7 as standard) this might explain the problem. However, try as I might, I can't find a successful way to slipstream DirectX into Win2k. All packs seem to only made for WinXP (e.g. Ryan's) and they break horribly in Win2k. I've tried ameding the inf files in various cab packs to make it Win2k compatible, but this still doesn't work properly. I don't want to use HFSLIP as it's way too complicated and it causes issues with NLite. Does anyone have any suggestions on how to solve this problem? Why can't NLite just slipstream DirectX like it does service packs?

I'm trying to do the exact opposite on my Windows 2000 install. Although each user does have a Temp folder (located in the Local Settings folder of their user account) there is still a useless Temp folder in C:\Windows that I would like to get rid of. I can't just delete the folder using a batch file because it's considered "in use" due to the two Session manager environment Registry keys that define TEMP and TMP as %SystemRoot%\TEMP. If I just go through and replace all instances of %%SystemRoot%%\TEMP with %%USERPROFILE%%\Local Settings\Temp in Yzöwl's cmdlines.txt example, will it prevent the creation of the %SystemRoot%\TEMP reg key and C:\Window\Temp folder so that I don't have to subsequently delete them?

Hi downwitch. Thanks for the heads up about this thread appearing in Google. I was hoping that it would save some people from going through the same grief as me, but I really wasn't expecting it to get anywhere the number one search result slot in Google (and especially not in just a few days). But it's great to know that people can easily find this thread if they need it. I'm glad to hear that the majority of your hair is left in tact. After my experience above, I'm still sporting the alopecia / chemotherapy look

No. It's not! (Dunno where it went though). I looked on another CD that was giving me grief (loads of missing files) and it's not on that either. However, if I go back to one from a couple of days ago then I can see nlite.in_ in \i386. I always use exactly the same method to make the ISOs though (using the last section of NLite) so I don't know why the latest few attempts have changed and have that particular file missing. I'll get investigating.

I think I am destined to never get a satisfactory custom install CD working. As soon as I fix one problem then another one rears its head I've just started getting errors during my text mode installs (in Windows 2000) due to nlite.inf. The error message displayed by Setup is: Setup cannot copy the file 'nlite.inf' If I press 'esc' to skip the file, then obviously this leads to an error later on in the installation. During 'Advanced Inf Install' the following error message appears: Could not locate inf file 'nlite.inf'. I have remade my installation (each time from fresh source files) but it makes no difference. Looking at the NLited files, I notice that I have an $OEM$ folder with only one file in it (cmdlines.txt - with one entry; "rundll32 advpack.dll,LaunchINFSection nLite.inf,U"). This is weird beacause I have made dozens of NLited discs over the last few days and up till now not once have I ever had an $OEM$ folder present (the only folder was the i386 folder). I don't know if this is because I may have used a different option for something (most of the options I chose are essentially the same as what I was doing before) or whether it's a change between NLite 1.21 and 1.3 (I don't think it is though, as I'm sure I've made Win2k CDs on 1.3 and they had no cmdlines.txt file in $OEM$ either). I can see the nlite.in_ in the i386 folder, so I don't know why it won't copy. I've used different media to rule out any CD defect preventing the file from being copied, but that also made no difference. I still get the same error message. Can anyone offer some advice on what the problem might be? (Obligatory NLite session is attached). Thanks LAST_SESSION.txt

Yes, that would work, but I was initially thinking more along the lines of "rem-ing" out the problem hotfix (e.g. with a semi colon) rather than simply documenting its failed integration. Otherwise if you re-load your lastsession.ini (which a lot of people will do) you will keep encountering the same errors over and over again, because NLite will keep trying to install the incompatible fixes that are listed in the [Hotfixes] section of the session ini (regardless of any notes at the end of the file). Automatic 'rem-ing' out these problem entries would ensure that (on subsequent use of the session ini file) these incompatible files would be skipped automatically, theyby not cause the NLiting process to stall on an error dialog waiting for user input to skip the file. Without this, the user is left to remove the entry manually, and unless they have a very good memory (or the foresight to write down each individual Hotfix string from the NLite error popup) then they're not going to know which files to remove because there is absolutely no indication of them after the NLite process has completed. However, you raise a good point about a section dedicated to errors. By moving the hotfix entry from the [Hotfixes] section (rather than rem-ing it out), it would make it much easier to find which files have failed to install. It would certainly be easier than searching for certain items preceded by a semi colon buried in a long list of entries. Also, the fact that the problem entries are no longer under the [Hotfixes] section would mean that NLite would not keep trying to integrate those files when that session file is re-used. Additionally, comments on the nature of the failure could be kept along side the hotfix entry to which it relates, without messing up the neat list of items in the [Hotfixes] section. This could not be done if the problem entry was REMd out 'in situ' (because any comments would be in another section away from the hotfix entries). I'm sure Nuhi could do basic text manipulation like that in his sleep (and with one hand tied behind his back).