Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Posts posted by Pyron

  1. Hi there, took me quite some time to recover my forum password...

    First of all, nice idea!

    The implementation in C++ is actually quite simple, but I didn't have the time to test it during an unattended installation. (just came home from work)

    Usage is like this:

    SetupCopyOEMInf.exe <dir with drivers in subdirectories>

    It scans a dir recursively and calls SetupCopyOEMInf for every .inf it finds.

    Windows may have problems when the referenced driver files are not in the same directory as the .inf, couldn't check that either.

    Feel free to try it yourself :)




  2. I just found this document :http://home.hiwaay.net/~pittman/archive/makecab.doc, which explains makecab/ddf files in detail.

    This is what it says about FolderSizeThreshold:

    Folders are compression/encryption boundaries.  The state of the compressor and cryptosystem are reset at folder boundaries.  To access a file in a folder, the folder must be decrypted and decompressed starting from the front of the folder and continuing through to the desired file.  Thus, smaller folder thresholds are appropriate for a layout where a small number of files needs to be randomly accessed quickly from a cabinet.  On the other hand, larger folder thresholds permit the compressor to examine more data, and so generally yield better compression results.  For a layout where the files will be accessed sequentially and most of the files will be accessed, a larger folder threshold is best.



  3. WDs are a bit picky about their jumpers, so when you say you set it to "master", I assume you mean you set it to "master/single".

    Has your mainboard an additional IDE controller onboard and did you connect the HD to that one? In this case you would need the drivers disk and use it by pressing F6 during textmode-setup.



  4. If this one would work as expected, there wouldn't be much difference. I prefer using my presetup.cmd, however, because I am much more flexible in what I do before setup starts and even afterwards before reboot. (Like uncompressing drivers before, setting registry keys, cleaning up, etc.)

    So it depends of what you need to to.

    Choice, the problem is choice.

    -- Neo, Matrix Reloaded



  5. Yes, I see clearer now.

    I assume the client is connected to the internet through your server. And you mentioned Microsoft's ISA server before. Therefore you have to configure its FTP-Proxy and your ftp-client accordingly. (I assume you use a seperate FTP-program, I would recommend it anyway).

    After a quick glance at google, you could also use ISA's SOCKS proxy, should save you some hassle if it works at all. If in doubt, search the manual for FTP or SOCKS.



  6. I just bought an AthlonXP 64 3000+ on an ASUS K8V SE Deluxe with an Arctic Cooling Silencer 64 Cooler. So far it's rock solid, didn't have any problems with it, except under linux (X freezes, but that has no high priority for me at the moment).

    And it does not get very hot, actually it runs cooler than the 1800+ I had before, on the past few summer days it got up to 52 degrees Celsius, so that's very ok for me.

    If you are a lot into numbercrunching (like seti@home) a P4 would likely perform better, due to hyperthreading.



  7. The two routers should have IPs from the same subnet, so

    would be okay.

    One more thing on the DHCP-server. The simple reason to disable the one in the WLANRouter is that the WLAN-Cards would receive their info from there first, ie gateway and dns information which points to the WLAN-router, not to the one connected to the internet.

    Which type of cable to use depends on the ports on the routers. If you have a port labeld "uplink" you take a straight cable from the uplink port of one router to a normal port of the other. If you have no uplink port, you connect them via a crosslink cable on the normal ports.

    The SSID is basically the name of the Wireless router, which can be broadcasted or not. You should disable the broadcast if possible, this adds a little bit to security.



  8. Okay, so now it's my turn to present a possible solution...

    Let's go back to the roots:

    Create a directory with your drivers, put SetDevicePath.exe in it. Compress the contents of this directory with WinRAR, make it self-executable. Put the following in the comment:

    setup=SetDevicePath.exe c:\drivers

    Put the resulting sfx-archive on your CD and start it with DetachedProgram in winnt.sif as usual.

    Here is the catch: I did not test it, as I don't use winnt.sif. So it would be great if someone could test this method.

    (I would have used 7-zip if wasn't so restrictive about sfx-archives)



  9. Try this:


    [HKEY_CURRENT_USER\Software\Microsoft\Driver Signing]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing]

    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing]



  • Create New...