ardnelias

You can check the SP2 executable that you downloaded. First extract it to a directory of your choice. Goto i386\Update folder under the folder where you extracted the SP2 executable. Open Update.inf and look for a line that reads: 'ThisServicePackBuild'. It should say 2180. [Version] Signature = "$Windows NT$" LanguageType = %LangTypeValue% NtBuildToUpdate = 2600 NtMajorVersionToUpdate = 5 NtMinorVersionToUpdate = 1 MaxNtBuildToUpdate = 2600 MaxNtMajorVersionToUpdate = 5 MaxNtMinorVersionToUpdate = 1 MinNtServicePackVersion = 0 MaxNtServicePackVersion = 512 ThisServicePackVersion = 512 CatalogFile = sp2.cat ThisServicePackBuild=2180 AllowUpdateBuilds = 2096,2138-2180

Open Control Panel->Administrative Tools->Local Security Settings on the left pane expand Local Policies and select Security Options. Now select the following setting in the right pane: Network Access: Sharing and Security Model for Local Accounts Right click and select properties. Change the drop down to "Classic - Local Users authenticate as themselves". Click OK and close all the windows. Now Right click on any folder in explorer and invoke the properties dialog. You should be able to share (just like in Windows 2000). Hope that helps...

Acronis Partition Expert is a good choice. Or you could try Partition Magic.

It coul be due to any no of problems. Have u installed anything after saving the game?like updated drivers?

Try this link http://www.flexbeta.net/forums/index.php?showtopic=738 Haven't tested these myself. So let me know if they work on MSN Messenger 6.2

The Day SP2 arrives, you are better of doing a clean install of XP - maybe with SP2 slipstreamed rather than hope to uninstall the prerelease and then install sp2.

@Joe User What you describe seems to be a solution to the problem in installing the fix. Can u please post the script you mentioned here in the forum. - A non AutoIT script would be even better - if u can manage one. Thanks...

Try resetting your Internet Explorer cache and delete the history. Do a thorough Virus scan with update defs. Use a Download Manager and try saving to a different drive. If you dont use a download manager, at least try using a browser other than IE: Firefox would be a good suggestion. See if downloading with these other progs has the same effect. If you get the same results then the issue has to be with Permissions related. In that case, you can try saving your downloads to a FAT32 partition.... Phew! lots of things to try....good luck

How To Use XP's DiskPart Commands http://www.wintrouble.net/discus/messages/53/5083.htmlThe command-line DISKPART utility in Windows http://searchwin2000.techtarget.com/tip/1,289483,sid1_gci953071,00.html?FromTaxonomy=%2Fpr%2F5e3You'll need to register with the website (free) in order to access the second article. Here is the MS website link to diskpart: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/diskpart.mspxHope its of use.

I put the mdac fix in a separate batch file and added it as a command in cmdlines.txt. Still no success - guess I will try adding the batch to RunOnceEx.cmd

Thanks Bee. I will test it and report back:)

I suggest you get Familiar Try Flashget / Download Accelerator Plus. Both do a good job. http://www.flashget.com http://www.downloadaccelerator.com/DAP7/Default.asp good luck

Hi I am trying to automate the installation for RASPPPOE - a PPP over Ethernet protocol driver for windows. Its freeware, and has several advantages over the PPPOE that comes with Windows XP. I tried to package it as an IExpress installer. But it turns out that doesnt work. Any suggestions on how to go about it? Here is a link to the actual package: http://raspppoe.com/RASPPPOE_098B.ZIPWebsite: http://www.raspppoe.com

@[bM]Crusher I''ll try putting the hotfix in its own batch file. Thanks for the advice BTW I am using XP Pro. @MasterControl The file is named properly - I double checked all the names with those in the batches. Thanks anyway. I'll test it again and let u guys know...

hi everyone, I followed the Unattended guide on MSFN and created a Windows XP SP1a cd with hotfixes and other apps. While everthing seems ok, I have trouble installing the MDAC hotfix Q832483. I put the install command: start / wait ENU_Q832483_MDAC_X86.EXE /C:"dahotfix.exe /q /n" /q inside a batchfile hotfixes.cmd and placed it under the $OEM$\$1\Install\hotfixes\ folder on the cd. here is my hotfixes.cmd: I am calling the hotfix.cmd from [GuiRunOnce] in Winnt.sif The install seems to complete well. But after checking the dahotfix.log file, I see that the install fails! Here is the relevant portion of the file dahotfix.log: What could be the problem? Anyone? Thanks for your help...

Using a Hex editor would be one option i suppose. You can see the ascii representation on the right pane of most such editors!

This behaviour occurs when you try to create an account with the same name as an existing account. For e.g if there is already an account with the name Sam - and if you are to add an other account with the same name, then windows appends the computer name to the account and it effectively becomes: Sam.laptop Have you tried creating a user with any name other than Sam?

hmm...Have you tried giving the hardcoded path say: c:\winnt\System32\drivers\winrt.sys

Trying chaning the Imagepath value to the following string: %SystemRoot%\system32\drivers\WinRT.sys This should get you the full path...

Java Update fails to apply changes to your system. Error 1722 http://java.sun.com/j2se/1.4.2/install-windows.html .

Have you checked the Event Viewer? Most services write their error events there. My guess is that it has something to do with the path string. If the string were given as REG_SZ type then you need to put two \\ 's instead of one to get the correct path. Check and let us know...

First off you haven't mentioned what OS you are using? If its XP, then most probably your installation boot files got messed up. You can pop in the XP cd and boot off your cd drive. Then try the repair option and see if its of any help. You will get a command line prompt asking to login to windows as administrator. Once logged in, you can try repairing your boot files using the fixboot command.