Jump to content

ToBe

Member
  • Posts

    220
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Sweden

Posts posted by ToBe

  1. I can't see any error about the product key section... Looks the same as mine. In the documentation for winnt.sif in ref.chm, located in the folder support\tools\deploy.cab on the cd they have quotations around the productkey:

    ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"

    But I don't have that, and it works for me..... :blink:

    You say you have a corp version, and 30 keys to use, but you only need one corp key for all installs... Thats what the corp key is all about.

    Are you sure you're using the right media/keys?

    Just a thought...

  2. Windows 2000 select media does not need any product key. You can check if it is a select media by opening the file setupp.ini file in the i386 folder. If the line pid=XXXXXXXX ends with a number higher than 200, it's select media.

  3. To make a transparent bitmap you must make sure that the bitmap has been converted to Indexed 256 colour. 24bit Bitmaps will not make a transparent image. Make sure that pixel (0,0) in the top left most part of the picture has the colour you want to be transparent.

    If you have a background colour that you do not want to be transparent put another colour at pixel (0,0), preferably 1 that doesn't appear in the rest of the image. Some image editors allow you to add a colour to the palette if needed.

    In some cases setting colour 0 in the colour index also can help.

    http://www.msfn.org/board/index.php?showto...nsparent+bitmap

  4. I've made a 700MB cd with Windows 95, 98, ME and 2000, so it can be done....

    Just delete all the unnecessary folders. Win95, Win98 and WinME install folders and the i386 folder from win2k is all that is needed, then make the iso with cdimage.exe.

    It was a while ago, so I don't remember exactly how I did it, I just know it's possible... :)

    Follow the guide to make a multiboot-dvd, and use the operating systems you want, and then make a cd instead of a dvd.

  5. Found this using google, gonna try it to see if it works:

    To make a transparent bitmap you must make sure that the bitmap has been converted to Indexed 256 colour. 24bit Bitmaps will not make a transparent image. Make sure that pixel (0,0) in the top left most part of the picture has the colour you want to be transparent.

    If you have a background colour that you do not want to be transparent put another colour at pixel (0,0), preferably 1 that doesn't appear in the rest of the image. Some image editors allow you to add a colour to the palette if needed.

    In some cases setting colour 0 in the colour index also can help.

    And here is the webpage quoted, with a freeware tool

    EDIT// works like a charm :)

  6. @Bilou_Gateux:

    SED file attached. Didn't save the original, but this one should work the same.

    @edmoncu:

    Did you use xpcreate? This workaround does not work with xpcreate atm, I get the same error when using it. Add it manually to svcpack.inf, and burn your iso.

    @WwTIPPYwW:

    So do I add the DX_Upd.EXE /Q:A /R:N line and remove the Q839643.EXE /Q /O /N /Z line?
    Both lines/files must be in the svcpack.inf, see my first post in this thread.....
    what is "Q832483.exe /C:""dahotfix.exe /q /n"" /q:a" about??

    This way you can install KB832483 from svcpack.inf instead of runonceex, for more info, do a search of the forum.

    yet another question - I don't have this in my INF file - please explain?

    [ProductCatalogsToInstall]KB826939.cat

    This has to do with the Security Rollup 1. See here.

    DX_Upd.SED

  7. yes......

    BUT

    as this is the XPCREATE forum, we're trying to get it to work FROM SVCPACK.INF as describe in the Microsoft docs. Not just trying to get it work, we already knew that way. It's the hard way we want to figure out.

    Thanks anyway.

    taken from page two of this thread...... :)

  8. Translated it said something about "not correctly signed by microsoft, it will not be installed." at the T9-T8 mark in the install. Guess it has to do with the dll's beeing registered, and has wrong filesize or something. But WU shows no updates, the hotfix shows up in add/remove, and the fileversion is correct, so it must have been installed anyway. :)

  9. Tried it with xpcreate, and WU shows no critical updates. The dx9upd.exe was placed in the SVC-PRE folder. I did get an error message at the end of the install, though, so more testing needs to be done. When I tried with my manual unattended install, I did not get any errors.

  10. I'm glad to hear that it's working not only here at my place for once :)

    It should be possible to repack the dx9ntopk.exe with the updated dll's. That should give the same result in the end, I think.

  11. Also, the DLLs are registered at about T-8 or something around tehre, in the finishing up stages....

    Oh, ok.

    I checked my localized (swedish) version, and at first reboot, a key in HKLM\SOFTWARE\Microsoft\CurrentVersion\Run called DXDllRegExE with the value %windir%\RegisteredPackages\{44BBA855-CC51-11CF-AAFA-00AA00B6015C}\dxdllreg.exe shows up.

    That's why I thought the dx9 dll's are registered at first logon.

×
×
  • Create New...