Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Posts

  • Joined

  • Last visited

  • Donations


Posts posted by GreenMachine

  1. Actually, I quess I was not on again ... but I am now!

    In the next few days I will be testing the latest hotfixes, and trying my darndest to get copies of XPCREATE to those who requested it.

    More soon!

  2. I will be "out of the office" until March 16th. I will be popping in and making sure there are no fires to put out, but I will not have access to my working system. That also means that there will be no usernames/passwords issued for XPCREATE.COM until I return. Please do not ask, nor look for "alternate" sources.

    See you soon!

  3. That it_ybd beat me again!

    Welcome, avanderbeek, to MSFN!

    Yes, if you start with an unmodified installation of XPCREATE.INI, and an original WIndows CD, XPCREATE shuold find all it needs to create a bootable ISO. If you enter the CD driver letter in XPCREATE.INI, it should produce a bootable CD. Works for most everyone ...

  4. Welcome to MSFN, th_moreira!

    My idea?

    Make an XPCREATE installation, adding nothing but the hotfixes listed on the XPCREATE Web Site. If the problem persists, post your LOGFILES.CAB file, and I can look into it. If the problem is gona, add your "customizations" one at a time until you discover the one that is causing the problem. As I've said so often before: work logically in little baby steps, and most all of the problems can easily be identified.

  5. Actually, he did find it shortly after posting. Just was a bit quick to jump the gun!

    I keep meaning to make a page to explain the different "error codes" that are generated. This was error 1003.

    One reason that this one bugged me, was that user's did not understand about 8.3 name creation, however, if it is not active, it is because the user itself disactivated it (it is on by default). Too many people "tweak" their machines without knowing what they are actualy doing ... Remember: if it ain't broken, don't fix it ...

  6. I suppose a good test would be to install Office AFTER installation, and see if the same WFP box appears. It may have something to do with the state of the OS during installation. I would certainly think that Office may need to update some system files, so it MUST have a mechanism to allow it to do so. Apparently, that mechanism does not work DURING setup.

    Just a theory ...

  7. From what I can see, there are no new updates, as promised.

    And yes, the Malicious Removal Tool has been updated. You should be able to simply replace the old with the new. Of course, some may prefer to simply add the registry setting, as MRT should not be finding anything on a fresh installation ...

  8. Let's see. One of the first things detected is the OS, SP level and OS language, so I already have that.

    I update DOSNET.INF according to Microsoft's specs, however, it is not quite clear on files in sub-directories (such as UNIPROC).

    I might do a plug-in thing, but again, I would really prefer to keep it generic. I will probably NOT add the sub-directories to DOSNET.INF in the first place, but that does not solve all the issues.

    To be continued ...

  9. Now that you mention it, I did have one installation that had a similar problem. I re-downloaded all the hotfixes, and it worked fine. Perhaps that outdated WMP was the reason?

  10. Hmmmm ...

    Yes, those express files are, indeed, the patches without the binaries, which are then downloaded. These hotfixes cannot be integrated. If just run from SVCPACK.INF, you would also need ab active Internet connection.

    As I understood it at the time (long ago ... ), those uncompressed files are used during the setup process, that is why they are uncompressed. It is the compressed versions that are not needed. Like I said, that was a while ago I looked.

    I'll have to look into Q329115.

    I agree: I will stop adding the sub-directories to DOSNET.INF. Also, I think long file names there can cause problems in DOS based installs.

    Thanks again, Bilou_Gateux. I just happened to pass by here again. You really should consider adding new posts, instead of updating your last one, so it catches my attention better!

  11. Welcome, Procyon, to MSFN!

    Thank you for your kind words. A very eloquent way to make your first post!

    I have not yet tried to install that update, but I did take a look at the package, and what I see indicates that it should be fine in SVC-HF1. Give it a go, and post your results!

  12. XPCREATE DOES update DOSNET.INF: perhaps that is where the problem lies. Most often, the problem is not in XPCREATE, but a conflict with other edits, either manual or automatic. As always, first make an XPCREATED CD that is tested and works, and then try your other modifications.

  13. No, the freeware version does not download the hotfixes. You can look at the "Current Hotfixes" page of the XPCREATE Web Site, of the sticky post in the Unattended Windows Forum.

    For further differences between the Freeware and the Commercial versions of XPCREATE, please see the "What Version FOr Me" web page on the XPCREATE site.

  14. One thing I forgot to add ... I believe as long as you have %SYSTEMDRIVE% in your registry setting quoted above, the file might re-appear after every time you run the "Add Hardware Wizard". That is why I suggest getting rid of the cause, not the symptom. For now, you can just clean that registry setting (change to %SystemRoot%\inf).

    Watch out for the bumpy roads!

  15. %SystemRoot%\inf;%SystemDrive%\ ...

    Something is putting %SystemDrive%\ in there, and it should not be. That is your real problem. I would try removing the OemPnPDriversPath completly, and I bet it disappears.

    Now, in answer to your question: YES, you may delete it. It is there to speed up searching for drivers when adding hardware, and is valid for the directory in which it resides. Without it, Windows will search all the INF files in the SYSTEMDRIVE (usually C:). Since there are usually very few files in the root of the SYSTEMDRIVE, chances are you will increase the time to search for drivers by a few milliseconds.

    Does that help?

  • Create New...