Jump to content

madmungo

Member
  • Posts

    25
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Australia

Posts posted by madmungo

  1. Hi, the update that causes the update loop for me is KB952709. Seeing as I remove QoS for AV files and this update improves the performance of Windows Vista SP1-based computers by reducing audio and video (AV) stuttering among other things. I suspect this is the problem.

  2. Hey guys just noticed this happened to me AFTER doing a fresh install and after a few reboots for software instalation that after doing a windows update with all (24) post SP1 updates that the firewall was stopped and when I tried restarting it it came up with the same error as in the first post.

    Have just copied the polstore.dll.mui file and am about to reboot to test. will report back in a sec.

  3. FEAR needs it. I have placed the x64 and x86 versions of gameux.dll into my ws2008 install and when I try and run fear it starts about 2000 instances of rundll and rundll *32 and slowly closes each one then pops up the FEAR has failed to start error message.

    Another game I have needs the dll file but I think it will do the same thing.

  4. I have no Idea what is causing it but if you change the burning engine from the internal one to Mkisosf then make your image it will work as it happened to me. If you burn the image directly to disk you do not get this error. This has happened with 3 different Windows cd's, one origional XP, one MSDN xp+SP2 and one XP VLK disk.

  5. @Happy_ct

    Just downloaded your files and it is being caused by the Play audio in WPI option being set to YES. Set it to NO and it works without errors.

    I also set this option in my config,to test, and get the exact same error. Same file and same line number. Dose not matter which of the 4.x versions used all create the same error when the Play audio in WPI is ticked.

    Hope this solves your problem.

  6. I had this problem and found out that I had an extra back slash in one of my programme install paths i.e, %CDROM%\\Install\setup.exe instead of %CDROM%\Install\setup.exe.

    In your config.js you need to check that there is only two back slashes in all of your install paths, will look something like %CDROM%\\Install\\setup.exe when correct.

    This was driving me mad and I was just about to give up when I started to manually edit config.js and found the error.

  7. This is taken from the Novell discussion Server novell.support.netware.client.winnt-2x-xp in reply to a similar question to yours.

    > Is there a release date (or beta date) for the Novell Client on

    > Windows XP 64-bit? Is there a client planned?

    Currently, Novell is still evaluating whether there is a real demand

    for a 64bit client. I suggest you let them hear your voice by

    submitting an enhancement request through

    http://support.novell.com/enhancement/

    Hope this help.

  8. Hi guys I have no problems whatsoever. Everything works like a charm.

    Here is what I did.

    1. Download the file in serialz opening post and extract.

    2. Open the html file and click on the link to pyrons post and grab the setup.ex_ file.

    3. Uncab the ORIGIONAL setup.ex_ file from your I386 folder with the following command expand SETUP.EX_ setupORG.exe and copy SetupORG.exeto your I386 folder.

    4. Copy the setup.ex_ you downloaded from pyrons post into your I386 folder.

    5. Compress your driver files as *.7z files. Only select the files inside the root folder of the drivers and name them acordingly.

    6. Put the Compressed Driver FILES inside the directory named ->$OEM$/Driverz.

    7. Put the following into you I386 folder, 7za.ex_ Presetup.cmd XRep.ex_ DevPath.ex_. From the file downloaded in step 1.

    8. Add the following lines to TXTSETUP.SIF under [sourceDisksFiles]

    7za.exe = 1,,,,,,,2,0,0

    Presetup.cmd = 1,,,,,,,2,0,0

    XRep.exe = 1,,,,,,,2,0,0

    SetupORG.exe = 1,,,,,,,2,0,0

    DevPath.exe = 1,,,,,,,2,0,0

    You should now be done. I did not use pyrons Presetup.cmd file only the one out of serialz pack.

    I also found that if you use this method you cannot use the driver integration of Nlite as the drivers added by nlite do not install.

    Edit: Fixed up Step 7 to use the corect files.

×
×
  • Create New...