• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About signal64

  1. I wanted to add the Intel ICH9R RAID drivers and not having much luck. Prior to running USB_MultiBoot2, I created Textmode directory under $OEM$ Copied iastor.inf, iastor.sys,, and txtsetup.oem to Textmode directory Added the following to winnt.sif [MassStorageDrivers] "Intel® ICH8R/ICH9R SATA RAID Controller" = OEM [OEMBootFiles] iaStor.inf iaStor.sys Txtsetup.oem I keep getting a BSOD after the storage drivers load in the text mode install. I used USB_MultiBoot2 with a USB Stick. I've successfully installed from a generated image before, but this is the first time trying to add the RAID drivers. Am I going about this the right way?
  2. At times I have seen some boards running USB 1.0 speed with certain USB CD drives when installing Windows. This is even though USB 2.0 is enabled in BIOS so was wondering if that was the issue in this case. I used bench32 for the speed test I mentioned earlier. Here's the results on my victim Abit NFM2 system I'm testing the install with. PQI 4GB: And for grins the Corsair 4GB Voyager GT: Now that things are clearer I did a quick install with the Corsair (FAT16) and text mode took about 15min to copy. I wasn't timing it closely as I was just seeing if it would work at this stage. If anyone is interested I'll do some comparison testing (and timing things closely this time) with FAT32/FAT16 on these sticks with a 680i motherboard. Need to load that puppy up again tomorrow.
  3. For whatever reason you can't use FAT16 on this 4GB stick (or the Corsair 4GB - it just arrived) using the HP USB Disk Disk Storage Format Tool. I had ignored the FAT16 requirement mentioned for PeToUSB as being needed for all and didn't see it as a requirement. PeToUSB did format the sticks as FAT16. Suggestion for a change to the wording to: BEFORE YOU START - Make sure you have a FAT16 formated USB-stick using the HP USB Disk Storage Format Tool or PeToUSB. Make sure you use "Enable Disk Format with LBA FAT16X" when using PeToUSB. or something similar. It might make it even better to mention up front you can't use some 4GB with the HP Tool (and obviously larger sticks will need some extra work). Ok - seemed to have missed that bit in the doc.
  4. Still waiting for the Corsair GT to get here so in the meantime decided to try this out on a generic PQI 4GB stick. 1. The text mode copy took about an hour. I bench'd the stick on the same system prior to the install and got 12MB reads. While not great, it seems it shouldn't have been that slow on the copy. I saw another reference here to larger sticks and fat32 being slow. The total space being used on the stick now is 522MB so going to try to partition it as 700MB with FAT16 for grins. 2. The key doesn't show as C: during the partition portion of the setup. Think this lead to the boot.ini issues that showed up after text mode install. And yes, I'm making sure the boot selection of the stick is done in BIOS. Stick was never removed. What's also kind of odd is when the stick had a dos image on it, it did boot up as C: System Info: Abit NFM2 - BIOS 214 Single PATA with 2 partitions (30Gig primary active + 200Gig primary) During text mode setup I deleted the 30Gig partition and selected it to install on. When text mode finishes, reboot, and select GUI, I got an error that is a bit misleading. "missing <Windows root>\system32\hall.dll" due to boot.ini telling it to look at the other partition (which has NTFS on it). I had to set the boot.ini GUI line to partition 2 (original had 1) on the stick for it to work. And of course it errored out trying to put a boot.ini on the hdisk after login. Had to manually put one on. The resulting install did end up with a C: So it looks like to setup I have 2 partitions but it's treating the second as C: and the first as D: which is weird (c: was partitioned first). I'm backing up the D: partition and going to nuke both and try again. So while off to somewhat of a rough start I have some things to try.
  5. Rats.. I just ordered a Corsair GT 4Gig just for this. Guess I'll find out if "wear leveling" is an issue when it gets here. By reading the doc though it doesn't look like it should be an issue. The addressing of data is the same to the computer, it's the lookup table in the stick itself that does the remapping and is supposed to be transparent to the system. It isn't doing this at an OS/FS level. But we shall see.
  6. Thank you, perfrmon does help out quite a bit. Page File Bytes Total and Page File Bytes by this particular process looks like they will be good enough. An issue I'm having is trying to scale in the Physical Memory Avail (2Gig installed, 1.7 after boot, and 1.2 after application loads). It would be perfect if the counter was a percentage as the current total doesn't scale very weill with those numbers. No way to change that I suppose? Thanks
  7. I'm in a bit of a heated discussion in regards to how a particular app is utilizing memory. I've been able to use Sysinternals Process Explorer to see a good chunk of info, but the problem is I can't find anything to show how much of the page file a particular process is using. I've also tried XTM but it still doesn't show this info. Is there anything out there that will show this? Example: Page File Usage = 350MB How much (if any) of that belongs to a single process? Thanks
  8. At this stage, I'm just trying to get an Adaptec Driver to load off of a floppy during a WinXP install using F6 and not having any luck. I'd like to at least get this part working before going further with unattended. Basically I can F6 and it'll load the driver, let me format the drive, and start the install. However, it'll eventually start complaining it can't find one of the files (dpti2o.sys) This is with the default downloaded drivers from Adaptec copied to a floppy. It looks like there isn't a problem with txtsetup.oem, but there is an issue with oemsetup.inf? I've tried adding a . or \ to SourceDisksNames, but it still complains. Any help is MUCH appreciated. Thanks. Disk Contents 08/05/2003 11:25 AM 10,739 07/31/2003 09:17 AM 1,368 ADPTMGT.INF 08/05/2003 11:25 AM 11,150 07/07/2003 01:34 PM 20,256 DPTI2O.SYS 07/27/2001 06:12 PM 53 DPT_I2O 08/05/2003 11:40 AM 451 DriverLanguageMap.xml 07/14/2003 08:27 AM 6,373 OEMSETUP.INF 07/14/2003 08:33 AM 3,111 TXTSETUP.OEM TXTSETUP.OEM ; ; Adaptec I2O RAID Host Adapter Drivers for 32bit Windows 2000, XP, & 2003 ; ; Text Setup Installation File For Microsoft 32bit Windows 2000, XP, & 2003 ; ; Version 1.11-32bit ; ; Edited 07/14/03 ; [Disks] d1 = "Adaptec I2O RAID Driver Disk for 32bit Windows 2000, XP, & 2003", \dpt_i2o, \ [Defaults] scsi = dpti2o [scsi] dpti2o = "Adaptec I2O RAID Adapters for 32bit Windows 2000, XP, & 2003" [Files.scsi.dpti2o] driver = d1, dpti2o.sys, dpti2o catalog = d1, inf = d1, oemsetup.inf inf = d1, adptmgt.inf [Config.dpti2o] value = "", Type, REG_DWORD, 1 value = "", Start, REG_DWORD, 0 value = "", Group, REG_SZ, "SCSI miniport" value = "", ErrorControl, REG_DWORD, 1 value = Parameters\Device, NumberOfRequests, REG_DWORD, 040 [HardwareIds.scsi.dpti2o] id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0011044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0021044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0031044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0041044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0051044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C00A1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C00B1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C00C1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C00D1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C00E1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C00F1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0141044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0151044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0161044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C01E1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C01F1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0201044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0211044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0281044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0291044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C02A1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C03C1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C03D1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C03E1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0461044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0471044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0481044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0501044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0511044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0521044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C05A1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C05B1044", "dpti2o" id = "PCI\VEN_1044&DEV_A511&SUBSYS_C05F1044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0641044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0651044", "dpti2o" id = "PCI\VEN_1044&DEV_A501&SUBSYS_C0661044", "dpti2o" id = "PCI\VEN_1044&DEV_A511&SUBSYS_C0321044", "dpti2o" id = "PCI\VEN_1044&DEV_A511&SUBSYS_C0331044", "dpti2o" id = "PCI\VEN_1044&DEV_A511&SUBSYS_C0661044", "dpti2o" id = "PCI\VEN_1044&DEV_A511&SUBSYS_C0341044", "dpti2o" id = "PCI\VEN_1044&DEV_A511&SUBSYS_C0351044", "dpti2o" OEMSETUP.INF ; ; Adaptec I2O RAID Host Adapter Drivers for 32bit Windows 2000, XP, & 2003 ; ; Installation File For Microsoft 32bit Windows 2000, XP, & 2003 ; ; Version 1.0p-32bit ; ; Edited 07/14/03 ; [version] signature="$Windows NT$" Class=SCSIAdapter ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318} Provider=%ADPT% ; ;If you update this version, make sure you also update ;the DriverVer field in the dpti2o_Install.NT section ; DriverVer=07/14/2003, [ControlFlags] ExcludeFromSelect = * ; ; diskid = description[,[tagfile][,<unused>,subdir]] ; [SourceDisksNames] 1 = %FLOPPY_DESCRIPTION%,dpt_i2o, ; ; filename_on_source = diskid[,[subdir][,size]] ; [SourceDisksFiles] dpti2o.sys = 1 [DestinationDirs] DefaultDestDir = 12 [Manufacturer] %ADPT%=ADPT [ADPT] %PM1554U2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0011044 %PM1654U2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0021044 %PM1564U3-1.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0031044 %PM1564U3-2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0041044 %PM1554U2_NO_ACPI.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0051044 %PM2554U2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C00A1044 %PM2654U2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C00B1044 %PM2664U3-1.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C00C1044 %PM2664U3-2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C00D1044 %PM2554U2_NO_ACPI.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C00E1044 %PM2654U2_NO_ACPI.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C00F1044 %PM3754U2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0141044 %PM3755U2B.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0151044 %PM3755F.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0161044 %PM3757U2_1.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C01E1044 %PM3757U2_2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C01F1044 %PM2865U3-1.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0281044 %PM2865U3-2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0291044 %2100S-1.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C03C1044 %3000S-1.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0461044 %3000S-2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0471044 %3010S-2.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0641044 %3010S-4.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0651044 %2400UDMA.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C05A1044 %2005S.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A511&SUBSYS_C0321044 %2000S.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A511&SUBSYS_C0331044 %2110S.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C0661044 %2405SA.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A501&SUBSYS_C05F1044 %2015S.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A511&SUBSYS_C0341044 %2010S.DeviceDesc% = dpti2o_Install, PCI\VEN_1044&DEV_A511&SUBSYS_C0351044 [dpti2o_Install.NT] CopyFiles = @dpti2o.sys ; ;If you update this version, make sure you also update ;the DriverVer field in the version section ; DriverVer=07/14/2003, [dpti2o_Install.NT.Services] AddService = dpti2o, %SPSVCINST_ASSOCSERVICE%, dpti2o_Service_Install, EventLog_Install [dpti2o_Service_Install] ServiceType = %SERVICE_KERNEL_DRIVER% StartType = %SERVICE_BOOT_START% ErrorControl = %SERVICE_ERROR_NORMAL% ServiceBinary = %12%\dpti2o.sys LoadOrderGroup = SCSI Miniport AddReg = pnpsafe_pci_addreg [pnpsafe_pci_addreg] HKR,Parameters\Device,"NumberOfRequests",0x00010001,0x40 HKR,Parameters\PnpInterface,"5",0x00010001,0x00000001 [EventLog_Install] AddReg = EventLog_Add_Register [EventLog_Add_Register] HKR,,EventMessageFile,%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.dll" HKR,,TypesSupported,%REG_DWORD%,7 [dpti2o_Install.NT.HW] DelReg = LegacyScsiportValues [LegacyScsiportValues] HKR,Scsiport,BusNumber HKR,Scsiport,LegacyInterfaceType HKR,Scsiport,SlotNumber [Strings] ADPT = "Adaptec I2O RAID Adapters for 32bit Windows 2000, XP, & 2003" FLOPPY_DESCRIPTION = "Adaptec I2O RAID Driver Disk for 32bit Windows 2000, XP, & 2003" PM1554U2.DeviceDesc = "PM1554U2 Ultra2 Single Channel" PM1654U2.DeviceDesc = "PM1654U2 Ultra2 Single Channel" PM1564U3-1.DeviceDesc = "PM1564U3 Ultra3 Single Channel" PM1564U3-2.DeviceDesc = "PM1564U3 Ultra3 Dual Channel" PM1554U2_NO_ACPI.DeviceDesc = "PM1554U2 Ultra2 Single Channel (NON ACPI)" PM2554U2.DeviceDesc = "PM2554U2 Ultra2 Single Channel" PM2654U2.DeviceDesc = "PM2654U2 Ultra2 Single Channel" PM2664U3-1.DeviceDesc = "PM2664U3 Ultra3 Single Channel" PM2664U3-2.DeviceDesc = "PM2664U3 Ultra3 Dual Channel" PM2554U2_NO_ACPI.DeviceDesc = "PM2554U2 Ultra2 Single Channel (NON ACPI)" PM2654U2_NO_ACPI.DeviceDesc = "PM2654U2 Ultra2 Single Channel (NON ACPI)" PM3754U2.DeviceDesc = "PM3754U2 Ultra2 Single Channel (NON ACPI)" PM3755U2B.DeviceDesc = "PM3755U2B Ultra2 Single Channel (NON ACPI)" PM3755F.DeviceDesc = "PM3755F Fibre Channel (NON ACPI)" PM3757U2_1.DeviceDesc = "PM3757U2 Ultra2 Single Channel" PM3757U2_2.DeviceDesc = "PM3757U2 Ultra2 Dual Channel" PM2865U3-1.DeviceDesc = "PM2865U3 Ultra3 Single Channel" PM2865U3-2.DeviceDesc = "PM2865U3 Ultra3 Dual Channel" 2100S-1.DeviceDesc = "Adaptec 2100S Ultra3 Single Channel" 3000S-1.DeviceDesc = "Adaptec 3000S Ultra3 Single Channel" 3000S-2.DeviceDesc = "Adaptec 3000S Ultra3 Dual Channel" 3010S-2.DeviceDesc = "Adaptec 3010S Ultra3 Dual Channel" 3010S-4.DeviceDesc = "Adaptec 3010S Ultra3 Four Channel" 2400UDMA.DeviceDesc = "Adaptec 2400A UDMA Four Channel" 2005S.DeviceDesc = "Adaptec 2005S Ultra3" 2000S.DeviceDesc = "Adaptec 2000S Ultra3" 2110S.DeviceDesc = "Adaptec 2110S Ultra3" 2405SA.DeviceDesc = "Adaptec 2405SA SATA Four Channel" 2015S.DeviceDesc = "Adaptec 2015S Ultra320" 2010S.DeviceDesc = "Adaptec 2010S Ultra320" SPSVCINST_ASSOCSERVICE = 0x00000002 SERVICE_KERNEL_DRIVER = 1 SERVICE_BOOT_START = 0 SERVICE_ERROR_NORMAL = 1 REG_EXPAND_SZ = 0x00020000 REG_DWORD = 0x00010001