I'm assuming this makes use of the 'linkd' command available in windows (if the linkd file is extracted)
Seems so I didn't know about that command.
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Tim81
Pages 1
I'm assuming this makes use of the 'linkd' command available in windows (if the linkd file is extracted)
Seems so I didn't know about that command.
OverFlow wrote:hidden feature? you mean like mapping it that way? or useing subst command...
huh?
I was saying that from what I read, that nothing outside of the I386 folder is seen... however, ironically the "$OEM$" folder still works like normal... Why can we not move the OEM folder contents into the $OEM$ and process the driverpacks in that manner or the exe's to $OEM$ and the driverpacks to I386 so they can be 'seen'?
Overflow's response was meant for me; I wrote:
So.... 2nd copy of i386 then....? (since windows does not use Symlinks.... or is there a 'hidden' feature that allows it?)
As Overflow earlier wrote:
nlite also has the same limit it just doesnt tell you you have exceeded it like we do ;-)
its a microsoft limit not a driverpacks limit that is why we came up with M2
but for this to work your I386 folder must be in the root or it wont find setup.exe.
yes \\share\i386
no \\share\clients\MS\xp\I386
(same configuration as an OEM disk)
So in order to have 1 copy of i386.... it would be great to have something like the unix Symlink feature....
Found a way to do it: http://www.pearlmagik.com/winbolic/
Using the $OEM$ should be working, all the contents is being copied .....
nlite also has the same limit it just doesnt tell you you have exceeded it like we do ;-)
Hmm I don't need to specify anything in winnt.sif to let it work (no oemdriverspath).... and no $oem$ dir.....
but for this to work your I386 folder must be in the root or it wont find setup.exe.
yes \\share\i386
no \\share\clients\MS\xp\I386
(same configuration as an OEM disk)
So.... 2nd copy of i386 then....? (since windows does not use Symlinks.... or is there a 'hidden' feature that allows it?)
Twig, that was the same problem I had when using a method 2 install....
As said using the method of integrating textmode mass storage drivers using Driverpacks BASE (m1) and the rest using nLite (don't use mass storage pack there as it wants to integrate textmode as well and that won't work.....) is currently working correctly.
And for network installs.... I assume the methode 1 should work..... but not all drivers can be integrated then... Or use the nLite method to integrate them in drivers.cab? Don't know what nLite exactly does when integrating them.....
Hmm booting the windows kernel by modifying them like this guide said didn't work for me too....
But the using the linux sed utility worked for me, explained here:
http://oss.netfarm.it/guides/ris-linux.php
Sed for windows can be found here: http://gnuwin32.sourceforge.net/packages/sed.htm
The above (windows-based) guide originates from http://www.boot-land.net/forums/index.p … topic=1961 but that forum was down a while, seems to be up again.
I have the integration of drivers working by using nLite to integrate the Driverpacks, except the textmode drivers.
I used Driverpacks BASE to integrate the textmode mass storage drivers.
Then started nLite to integrate:
- RyanVM's updatepack, WMP11, .NetFramework and the DriverPack drivers (excluding mass storage).
After doing so, the installation appears to be working fine. RVMIntegrator breaks the install (iframework.dll issues), so therefore tried nLite instead.
And no, I don't install over the wireless network (altough there is an integrated wireless networkcard in my system and recognized by Windows correctly using the wlan pack).
As far as I know, it is not possible to PXE-boot over wireless.
I recently started to test out PXE-based install of Windows by using a thirdparty BINL server / TFTP server, so not using Microsoft's RIS, which requires a domain controller with active directory. The M1 method might work (not actually tested at the moment, as when using it, not ALL drivers will fit in the oemdrivers path in winnt.sif)... but M2 method is currently broken for the PXE method as Windows setup will complain that the fake setup.exe from driverpacks cannot be found dunno the exact message, but it comes to that
If anyone has a 2nd PC (or just VMware) and wants to try out the PXE based install...
http://www.vmware.com/vmtn/appliances/directory/232 for the Linux-based PXE server with Windows Remote install support (works out of the box). Or http://www.vhware.org/Guide_From_Base_I … FTPD32.rar to make your Windows XP (or possibly W2003 server too) a PXE/RIS server.
Pages 1
DriverPacks.net Forum » Posts by Tim81
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 2 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.014 seconds, 6 queries executed ]