Jump to content

trefrog

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

About trefrog

trefrog's Achievements

0

Reputation

  1. Ok. I was about to take a little break from this, but it's bugging me now. I restored the factory partition (glad I backed the thing up - thank Acronis!... and USB/IDE adapters) and just went back to square one (yawn), because I need my laptop (and my 2G stick) in working condition for the rest of the week. The page that led me (back) to msfn.org when looking for a solution for USB XP install had an interesting comment about a change made to a line of code that fixed their own particular problem with the biosinfo.inf message. This is apparently a page regarding an older version of this script package. I searched the USB_MultiBoot3 folder for the text SET __xpdir.!dtel!=%%H and found: 1 instance in BT_folder2.cmd 1 instance in CMDCONS_Folder.cmd 1 instance in USB_MultiBoot3.cmd I don't know which of these scripts/sections actually run during my setup, but the snippet is the same in each: SET cpyflag=0 SET /A dtel=0 FOR /F "tokens=1,2* delims== " %%G IN (%xpsource%\I386\DOSNET.INF) DO ( SET FTAG=%%G IF "!FTAG!"=="[Directories]" ( SET cpyflag=1 ) ELSE ( SET FTAG=!FTAG:~0,1! IF "!FTAG!"=="[" SET cpyflag=0 IF "!cpyflag!"=="1" ( SET /A dtel=!dtel! + 1 SET __xpdir.!dtel!=%%H ) ) ) Now I'm looking at my DOSNET.INF and I'm seeing this: [Directories] d5=\ d1 = \I386 d2 = \cmpnents\tabletpc\I386 d3 = \cmpnents\mediactr\I386 d4 = \cmpnents\netfx\I386 I'm not a major pro with batch scripting, but if the delims are '=' and ' ' (right?), then wouldn't that first line give something different? I don't know... it just sticks out for being different. I think I did try changing that line when I was working with the old version before I found this board... obviously I abandoned that whole branch. I'll attach the whole DOSNET.INF anyway. My XPSOURCE is in the physical CD-ROM (L:) VX2PVOL_EN I don't quite get what you're saying here... the root folder on L:\ contains I386... or do you want me to point to I386 directly? My USB_MultiBoot3 folder is on root of C:\ to avoid any "spacing problems" (if any) I can try the clean source idea, but it will have to be like... 2 weeks from now when I'll get a weekend to myself at home. DOSNET.INF.txt
  2. Program - USB_MultiBoot3.cmd - 14 feb 2008 - Date = 19/02/2008 0:26:44 Prepares MultiBoot USB-Drive provided with Windows XP Setup LocalSource Supports Booting: MS-DOS FREEDOS BartPE WinPE 2.0 and Setup Windows XP Supports GRUB4DOS with DOS FLOPPY IMAGES + Linux and Supports SYSLINUX Menu *** BEFORE YOU START: *** Use 2 GB USB-stick with High Read/Write Speed First Format to Make Bootable USB-stick with FAT FileSystem, FAT = Faster such that USB-stick has NTLDR Bootsector and is seen by BIOS as Harddisk PeToUSB Settings: To Format USB-Drive : Enable Disk Format with LBA FAT16X For Install of BartPE: Give BartPE Source Path and Enable FileCopy OR Use Existing USB-stick with NTLDR Bootsector and Multi boot.ini Menu GUIDE: [url="http://www.911cd.net/forums//index.php?showtopic=20089"]http://www.911cd.net/forums//index.php?showtopic=20089[/url] For AUTOSTART: COPY PeToUSB.exe in your USB_MultiBoot3 folder PeToUSB Download [url="http://gocoding.com/page.php?al=petousb"]http://gocoding.com/page.php?al=petousb[/url] For UNATTENDED XP Install make Changes in USB_MultiBoot3 folder: Change Product Key in winnt.sif and Change $OEM$ folder to your needs FOR USB-Harddisk make 1900 MB partition at beginning of the USB-Harddisk Use FAT Format and Set Active OR use PeToUSB to Format such partition ============================================================================= PeToUSB.exe was launched to FORMAT USB-Drive DriveList FAT FAT32 NTFS drives = D: E: G: H: I: J: K: M: N: Q: mkbtpath = C:\USB_MultiBoot3\ usb_type = USB-stick xpsource = L:\ usbconfg = X_CONTENT usbdrive = N: usb_temp = usb_xpbt MOST part of the post deleted by jaclaz
  3. Is this intended for SP2? I thought I was doing something wrong when I kept getting biosinfo.inf could not be found in $WIN_NT$.~BT, then I noticed that nLite was deleting alot of files, so I decided to only use it to integrate KB updates, which caused absolutely no deletions, mostly just additions + changes (checked with ExamDiff). Then I saw how it's supposed to work with the $OEM$ folders so I customized the reg files and added my switchless installers (with modified nLite.cmd makecabbed back in -> NLITE.CM_) Also I made some changes to winnt.sif to match some of what was happening in nLite. This is what I confidently believe to be a 'loaded' XP CD, as opposed to 'stripped'. What could be going wrong? Is biosinfo.inf supposed to be in $WIN_NT$.~BT, or is it (wherever this reference is coming from) supposed to be pointing to where the file is actually ending up: \$WIN_NT$.~LS\I386\ ? I'm going to try attaching my log file. (lots of copy errors in there) BTW, I'm using a Lenovo 3000 C100. My CD Rom drive is dead, so I have to do this. One partition, formatted NTFS (do I need to format this clean again?) USB likes to take C drive (could not attach: Upload failed. You are not permitted to upload this type of file) will post...
  4. Tried that. Still didn't work. I don't believe the ulz is even decompressing, and I know it's not copying the ul to WUD dir, like it's supposed to. I'm running it out of J:\Program Files by the way, which isn't my official Program Files dir (C: partition is too small due to my nLite attempt only half finished - the goal being to seperate the WINDOWS dir from Documents and Settings, Program Files and pagefile.sys as well - a pristine windows partition - FYI), if that has any bearing on the issue... All my other programs run fine this way so far, I just change C: to J: whenever I install something. this was only intended to be a temporary install for testing my nLite build... moons ago. Edit: oh, when I run WUD first before opening the ULZ, a new instance opens up with the not found message and stays open. It's definitely not supposed to do that, I'm sure.
  5. mine isn't working that way for some reason. It's been a while since I ran it, but today I noticed the ulz extension wasn't registered to WUD, so I uninstalled and reinstalled WUD. The association was restored, but when WUD opens after running the ulz it still says no update list was found. Seems that the file is being passed into WUD, but it doesn't know what to do with it, so it doesn't act to decompress & create any new ul file.
  6. I'm not totally sure how it works, but it works for me. At some point it complained about not having a Modify Partition tag, and another time that it was improper - so I'm not sure if <!--ModifyPartition /--> is needed (it's commented out!), haven't tested that yet. I left it in as soon as it made it thru setup. The <DiskConfig> element only allows formatting of the system drive. To get around this limitation, I made a PreSetup.cmd script to run DiskPart and format. Its all in the "\Docs\WinFLP Installation Guide.htm": a good read, though a little vague. PreSetup.cmd: @ECHO OFF ECHO This CD will wipe your computer and reinstall Windows. Everything will be lost. ECHO You have 20 seconds to answer... CHOICE /c:YN /t:N,20 Are you sure you want to do this? IF %ERRORLEVEL% EQU 2 EXIT CLS ECHO You have 10 seconds to answer... CHOICE /c:YN /t:N,10 EVERYTHING will be LOST! Are you TOTALLY sure? IF %ERRORLEVEL% EQU 2 EXIT CLS diskpart /S .\install\diskpart.txt format C: /fs:NTFS /v:Windows /q /a:512 /c format D: /fs:NTFS /v:Paging /q /a:64K format E: /fs:NTFS /v:Stuff /q /a:512 /c regedit.exe /S .\install\setup.reg EXIT diskpart.txt select disk 0 clean all create partition primary assign active select disk 1 clean all create partition extended create partition logical size=216 assign create partition logical assign Unattended.xml <snip> <DiskConfig> <Disk ID="0" WipeDisk="Yes"> <CreatePartition Label="Windows" Size="*" Letter="C" FileSystem="NTFS" AllocationUnit="512" QuickFormat="Yes" FileCompression="Yes" /> <!--ModifyPartition /--> </Disk> </DiskConfig> I'm testing this on a Really old P-233 with 2 small HDDs (815 & 515). It actually runs! And suprisingly smooth to boot! Now the main problem I'm having is registry settings and hotfixes etc. from <RunOnce>. More on this later... also FileCompression on C: doesn't seem to kick in like it's 'supposed to' - if it's actually supposed to compress the contents on the fly?
  7. Yeah. I was wondering a little if the order the hotfixes are applied matters... I sorted them in Nlite by release date as I've seen recommended by someone, had to manually move a couple of them. I have IE7, WMP11 and Live Msgr. This sounds like a VERY IMPORTANT issue, so that i'm not using outdated, unstable and insecure DLLs! Could you point me to a list that illustrates the order to list them in Nlite? thx
  8. this is what i get after first logon: Current SPTD installation cannot be validated by setup. It is recommended to disable SPTD service and retun setup after reboot. Do you want to disable SPTD service now?
  9. Oh, also, is there a way to only install the CCC if an ATI card was detected?
  10. It seems this version of Catalyst is a different kind of beast than the last one. I've been looking at other threads about this, namely this one. My current Catalyst works fine, but I'd like to install this latest version. I did a little test, I don't know how revealing it really is, but I have to assume that the same mechanisms for installing drivers in windows are used for setup. I tried to install from the device manager. Instead of a 2KXP_INF folder, there's $OUTDIR, which has all the files that 2KXP_INF has except there's no subfolders. The Wizard asked me where ati2mtag.sys is. This doesn't look like a very good sign for an unattended install! Does anyone know how to install this via WINNT.SIF? I don't want to do it any other way, if I can help it. thanx
×
×
  • Create New...