prathapml

He is doing this with win2k.... So yes your limitation is 256 chars. WinXP/Svr2k3 raises the limit to 4096.

Yes. You need to re-patch the uxtheme.dll (with an updated patcher) to fix this.

You might have got infected with the blaster worm. Slip-stream SP2 into XP disc and re-install, or install SP2 before turning your modem on.

And the above method might end up rebooting your system halfway thru setup because the driver installer wants to. The method for XP and 2k is the same - use OEMpnpDriversPath. It will work if your drivers aren't inherently defective.

No one wanted an invite since 4 days? Anyways, the above wasn't meant to scare off posting, it only meant do not mention your email address And there's more treats......Visit - http://gmail.afraid.org Of course I have my doubts about whether it really works... They claim to have dispersed 71k+ invites.

weird

hi syskplim, reg.exe may not exist in win2k. It was part of the resource kit back then, and made it into the base OS later (winxp). But regedit.exe is what you need to apply .REG files - so you don't need to worry, unless you do value modifications from command-line. For your other questions, the search function would be better..... it has all been discussed more than once.

It works perfectly fine for me. The key is to stick to current, signed/stable drivers. Instead people normally get carried away by version-number-love, and go for whatever latest they see even if it is beta. Get this driver: http://www.nvidia.com/object/winxp_2k_66.93 It works properly on XPSP2 and 2kSP4 for me.

Yup. Imagine how small it would be if we could Netop FEAD our AIP! :bonkers: (10 MB *dreaming*)

A repair or re-install normally does not start on a clean slate - old junk is still around which can cause problems again.

Well, you already know this one: /s /v/qn(s for telling installshield to install in silent mode, v to pass values to MSIEXEC, qn/qb is the MSI switches) InstallShield switches described That -p is added by the FEAD optimizer it seems, to extract silently. So with that above combination of switches, you can keep the original downloaded package and install silently. The downside? A truckload of HD space is lost on nonsense! You will have 100 MB almost, of disk-space occupied with that switch. Instead, do our normal method of picking up the extracted files and making AIP of it (and install using much simpler /QB switch), and hardly 30 MB is lost. @Whisper Don't worry about the above - continue using your current switch, because it is easier.

Hello greghill, Welcome to MSFN forums and enjoy your stay!

Hi Jamall, The answer to this depends on what you do with your installation. If you are a version freak and want the latest version all the time, then go for NAV2006. Otherwise, stick to 2002 itself. The newer versions has nothing useful to FORCE you to move to the new one. Some of the main new additions is: 1. Instant Messenger Protection - this is idiotic if you know what you're doing 2. Scan within compressed files on every run - slows down your PC 3. Lot of components loaded all the time - occupies lot of RAM 4. Updated WMI for compatibility with XP security Center - not really needed 5. Activation - need this headache be explained at all? So as you see above, the main features/highlights of the newer ones is quite useless. All other features is same as NAV2002. I'm happily running NAV2k2 on many client machines with no problems at all.

If its Nero you use to burn ISOs, there's no CD/DVD dialogs to get involved with. Recorder >> Burn Image >> (browse and choose ISO) >> Burn.

Please see the rules of the forum which says, give appropriate name for topic. * closed.

* topic cleaned up Hello Whisper, Welcome to MSFN forums! I see that you are using the [GUIrunOnce] method, which is the best to start off with. Now what happens, is that as far as your windows knows, there isn't any %cdrom% variable - it will exist only if you set it. Now, setting it is a long process, so let's go the easier way. Below is what what you need to do, if you have anymore questions, do post back here. 1. Ensure that OEMpreInstall is set to YES in winnt.sif 2. Change all instances of %CDROM% to %SYSTEMDRIVE% Why is step2? That's because whatever files you have kept in "$OEM$\$1\" will get copied to your C: drive if oempreinstall=yes. And also, one thing to know is that the OEM folders on cd, do not actually mean ANYTHING at all to the windows setup - it is useful only because the preinstall=yes will copy files from within there to the corresponding folders on HDD. What is %systemdrive% ? It is a system variable, which refers to the partition where windows gets installed. We use that, to make the installs easier. For example, tomorrow if you chose to install windows to D:, even then your automatic setups should work, right? That's what its for. Hoping this helps.... Please post back on how it goes! :

Ah, those are COOL additions!

Then there's nothing wrong with the method! You are using beta drivers, or unsigned drivers which are not the best to play with. Get a proper driver downloaded from here - nVidia driver download. It works perfectly for me, and for everyone who has done this, so it will for you as well. Do post back with results!

I would say, set automatic updates according to how you like it, then export this key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto UpdateThere! Does that work?

Does it boot fine into a win98 DOS boot disk? Or better, a bartPE rescue disk? if so, you can copy away required files from C: drive to some other partition. Then just use a friend's PC to do the slip-stream to CD, and bring the cd and format C:, re-install. B)

I would say just use the standard tool to create the answer-file: latest deploy.cab, download page. The Setup Manager in that package is what you use to create your answer file, I hope? It will make it in the right way, *WITH* the licensing setup as well. Do post back with results.

slip-stream SP2, do a clean install. will take less time than what it'd take to find out what's happening.

duh! Don't look at me like that, I don't know.... I saw somewhere that the latest ATi (or was it nVidia ) Control Panels uses that switch now.

Time for your uA CD to crawl out of its shell and get to work....

There's nothing you need to do to get this. It will come easily by itself - use the OEMpnpDriversPath method to include nVidia forceware drivers.