Jump to content

meostro

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About meostro

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

meostro's Achievements

0

Reputation

  1. edit: okay, I'm thinking of the wrong "Method 1"... you're talking about the BtS method 1 where it calls the files in the M1 folder, not the "include drivers on your xpcd" method 1. I finally got it at 1:30 this AM I'm putting a modified version of CABfiles together with support code to extract the 7zs, in the end it should act like BTS_DPs_Slipstreamer.cmd for those of us that are just looking to create a driver CD instead of an integrated Windows install CD with drivers. I'll post it as soon as it's done, probably this weekend just to work out all the bugs. As soon as I test and see this works I think a donation is the least I can do, this will save plenty of time trying to find the right CD for whatever, it's all just in one spot. @Bâshrat the Sneaky: In CABfiles_M1.cmd, should this if /I %naam:~-2%==cab goto end be this? if /I %naam:~-3%==cab goto end (Also, BASE/FILES/Install_Instructions.htm has a broken link, missing a : between drivers and driverpacks for Slipstreaming BTS DriverPacks.)
  2. I can't speak for danutr, but I would really like to fit all of the drivers on a single CD, so anytime somebody needs a driver I can hand them one CD and Windows can auto-detect and install. I've tried all the variations I can think of to shrink this stuff: CABs, ZIPs, CABs of everything except the INFs, a "compressed" CD, but nothing works right. As-is, I just leave out the Sound drivers (since sound != system critical) and it fits fine on a 650MB CD.
  3. @Asin: There is no WINNT.SIF on my image, even after I SYSPREP it. That will put a significant damper on adding more drivers. @traxx2060 That's what I'm trying to do, create a single image for disparate computer systems. I'm working my way through that link, but Wally writes like he's got ADHD... The pointers and even step-by-step instructions are a little incoherent and fragmented. @D8TA That's what i'm trying to do, but I don't want to fork over the $xxx to have someone else do it. A.) It's not in the budget - and - B.) I want to figure it out myself to share with y'all. Anyone else have ideas? Or just more coherent pointers similar to Mr. Beck's?
  4. I didn't think the SIF method worked after the computer was installed for the first time... I'll have to take a look! I think I can get into the image before it's booted, I'll take a look at the DELL folder to see how they have it set up.
  5. I'm trying to create a single XP image to be deployed across our enterprise. Currently we have about a hundred different images across maybe ten hardware platforms from 4 different vendors. We've standardized purchases going forward, so we're down to supporting four platforms from 1 vendor - 2 desktop and 2 laptop configurations from Dell. The machines are similar enough that we are down to two images, one for desktop and one for laptop, but I've been tasked with creating a single image that can be deployed to either machine. I know at a minimum I need to get mass storage and chipset drivers in the image for every platform I want to support, I just don't know how to do it. I think it would be really cool to support any hardware on any system, ala Bâshrat the Sneaky's Driver Packs, but I don't know how to integrate them into an image (as opposed to an install CD). Whatever I end up with will be SYSPREP'd and packaged up for deployment, so if any of its switches or the mini-setup will do what I need that would be perfect. If there's no good reference out there on doing this, I'd really like to write one, any input would be appreciated.
  6. From the MS docs on installation formats here and here, the format used for the SourceDisksFiles section in TXTSETUP.SIF makes no sense to me. Some of those MS docs imply that I could CAB any number of these together and just reference a different source in the SIF, but the docs also say the format of SourceDisksFiles should be filename = diskid, subdir, size I have a line that looks like this accessS.chm = 1,,,,,,,21,0,0,access.chm which means, AFAIK: copy accessS.chm from disk 1 (1 = %cdname%,%cdtagfilei%,,\i386) to C:\WINNT\Help (21 = Help) and rename it to access.chm But what the heck are all of those ,,,,,'s in between, and also what are the 0,0,s? Some lines have values for those in the middle, implying that there are alternate sources or destinations or something for these files, but I don't see anything that shows what they really mean. Anyone have a good pointer (probably somewhere in these forums) as to what the other fields are? I'll update this section below as I figure out and/or get any reference values, assuming it may be of use to others in the forum: srcname = srcdisk, unk2, unk3, unk4, unk5, unk6, unk7, destinationdir, unk9, unk10, destinationfile
  7. @boooggy: Already did that part, that's where I end up with the SP1.CAB et al. It's slipstreamed into the build, but it's still taking up more space than it needs to. @RyanVM: Thanks for the pointer, that's exactly what I'm looking for. I'm going to try the same sequence with CABARC instead of EXTRACT/MAKECAB, hopefully it won't mess up the CAB structure that MAKECAB has in the .DDF you create. The bonus is that I can specify LZX with 21-bit something-or-other to get a couple extra MB of compression. I'm trying to integrate the Server 2003 SP and patches, that's why i'm working with SP1 instead of the usual XP SP2. I have to document my build 100%, so I can't use nLite since its functionality could, at some point in the future, possibly change. Yes it's ridiculous, but it's how I have to do it. If drivercabfix doesn't already do it, there's also another bit that should be removed from the TXTSETUP.SIF under the SourceDiskFiles section: sp1.cab = 1,,,,,,_x,39,0,0 Along the same lines, would it work to add all of the *.??_ files to the DRIVER.CAB or a separate CAB with a pointer in DRVINDEX.INF (or something similar) to consolidate about 5000 individual files into one? I'm looking through the disc now to see where the pointers for SHELL32.DL_ are, that should give me a start to see where setup is getting its file listings from.
  8. Howdy y'all! I've been reading through all the great unattended / slipstreamed / slimmed down installation info at unattended.msfn.org, plus a bunch of stuff on gosh's and RyanVM's sites. Goodness gracious great balls of fire there's a lot of info on unattended / universal XP installs! My problem comes from a bit of info I've seen, but haven't seen any details about. Some sites mentioned that nlite (and maybe some other programs?) will integrate a service pack cab into the main DRIVER.CAB, but i'm trying to figure out how to do such a thing manually. Is it as easy as I think? 1. Unpack DRIVER.CAB (cabarc x driver.cab driver\) 2. Unpack SP1.CAB on top, replace any duplicates (cabarc -o x sp1.cab driver\) 3. Re-pack DRIVER.CAB (cabarc -m lzx:21 n driver.cab driver\*.*) I'm a little leery of trying that straight-away since I also see SP1.CAT and win51is.SP1, I think it'd be a good idea to check with the experts (that'd be you) to see how you do it properly.
×
×
  • Create New...