1 Topic by vipejc

(1 replies, posted in BartPE - UBCD4Win - WinPE)

I'm trying to add SATA/RAID drivers to my BartPE disc to future-proof it if I ever decide to buy a SATA hard disk. (This 2004 mobo does have two SATA 1.5 Gbit/s ports.)

I followed Bart's instructions, but the directory structure of the instuctions doesn't match mine, so I tried filling in the blanks the best I could by copying and pasting files and folders to match it as closely as possible.

Is the directory structure critical to making added drivers work, or is it enough to create a custom folder and add txtsetup.oem, filename.cat, filename.inf, and filename.sys inside it?

Bart's directory structure
drivers\SCSIAdapter
drivers\SCSIAdapter\adpu320
drivers\SCSIAdapter\Create a folder here and put the storage drivers in it
drivers\SCSIAdapter\adpu320\MAXIO64K.REG
drivers\SCSIAdapter\adpu320\README.TXT
drivers\SCSIAdapter\adpu320\TXTSETUP.OEM
drivers\SCSIAdapter\adpu320\U320DSK1
drivers\SCSIAdapter\adpu320\WIN32BIT
drivers\SCSIAdapter\adpu320\WIN32BIT\ADPU320.CAT
drivers\SCSIAdapter\adpu320\WIN32BIT\ADPU320.INF
drivers\SCSIAdapter\adpu320\WIN32BIT\ADPU320.SYS

My directory structure
drivers\SCSIAdapter
drivers\SCSIAdapter\VIA V-RAID (Are spaces allowed?)
drivers\SCSIAdapter\Create a folder here and put the storage drivers in it
drivers\SCSIAdapter\VIA V-RAID\XPX86.oem (The driver package didn't have a "txtsetup.oem.")
drivers\SCSIAdapter\VIA V-RAID\VRAIDDrv
drivers\SCSIAdapter\VIA V-RAID\VRAIDDrv\XP
drivers\SCSIAdapter\VIA V-RAID\VRAIDDrv\XP\x86
drivers\SCSIAdapter\VIA V-RAID\VRAIDDrv\XP\x86\viamraid.cat
drivers\SCSIAdapter\VIA V-RAID\VRAIDDrv\XP\x86\VIAMRAID.INF
drivers\SCSIAdapter\VIA V-RAID\VRAIDDrv\XP\x86\viamraid.sys

pebuilder.log
Processing INF file "C:\pebuilder3110a\drivers\SCSIAdapter\VIA V-RAID\VRAIDDrv\XP\x86\VIAMRAID.INF", class "SCSIAdapter", provider "VIA Technologies, Inc.", version "11/26/2010"
Unsupported device class: SCSIAdapter
Don't worry pebuilder will use: txtsetup.oem
Collecting files done

Also, I don't see VIAMRAID.INF on my BartPE disc when I explore it.

Go to forum: BartPE - UBCD4Win - WinPE

2 Reply by vipejc

(16 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

I could turn that book into a volume set... Hearing you loud and clear!

My advice would be to stock up on some replacement parts now... tongue.

Jeff

LOL @ volume set

Already stockpile parts. See this way if I ever do build a system in the very distant future, I'll really be getting a bang for my buck. I'll just keep buying the same replacement motherboard that supports XP. I even burned a perfect ISO of XP Home with Service Pack 3 slipstreamed and talked Microsoft into giving me a free product key. I have this all worked out. I'm always prepared. BartPE, ghost image, disabled OEM tattoo check - Microsoft's no match for me. ;^)

Go to forum: DriverPack Mass Storage

3 Reply by vipejc

(16 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

I doubt that... i expect IDE emulation to disappear... It is already being phased out on many platforms. You don't see MFM and RLL support any more do you?

Probably you will jsut need to be careful when you purchase...
Make sure you buy a MB that has XP SATA drivers available. tongue

I really don't know why you think you will be running XP on hardware 20 years from now or even 8 years from now.

although i must admit i have a DOS 6.22 and win 3.11 box here with a 5 1/4 floppy and a QIC drive in it... BUT it is running on a DFI Socket 7 with a 486 processor.... Just because it won't die. I would also like to point out it is just a conversation piece and something to show off like an old trophy. The point is if you want to run a 20 Year Old OS run it on a ten year old platform.

If it is because you have some softwware you are married to... Then simply run it in a Virtual Machine. OR Windows 7 has a XP compatiblilty mode... whereby the XP kernal is loaded into ram with the Win 7 kernal and that works very nicely.

What is it you hope to achieve?

To use 32-bit Windows XP Home with Service Pack 3 for the rest of my life. I spent seven grueling years learning hardware and software - tweaking the system the exact way I want it - cleaning the file system of ALL junk folders and files. I don't have the desire, time or energy to do it again.

I still use dial-up because it's dirt cheap and does the job. I don't upgrade unless it's NECESSARY. I know my system like second nature. My boot time is under 20 seconds. I can run my system over two years without rebooting! My system has crashed only once or twice in seven years. Buying and repairing hardware is a snap... 

If, and it did, the system met all my needs in 2004 and my needs haven't changed, this system will continue to meet my needs in 20xx. Computer companies hate consumers like me, because I'm not stupid and see right through them. Only a fool would upgrade to Windows 7 or fall for one-percent-hardware-performance increases. Microsoft and Windows are stupid. For example, XP's NTBackup doesn't even support backing up to CD or DVD. Yeah, because every XP Operating System is under 1.44 MB and everybody uses tape drives. LOL What MicroSTUPID employee's idea was that? I could write a book about everything wrong Microsoft does - especially Windows.

Go to forum: DriverPack Mass Storage

4 Reply by vipejc

(16 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

it is unlikely that future chipsets drivers will be written to support XP. the current chipset drivers are probably the last of the line. EOL for XP is in two years.

If you slipstream Chipset and Mass you are good to go. Much as our Mass storage drivers are all inclusive so are our Chipset drivers. I can't garauntee that you will not have to update your disc over the next 20 years... But you can't do any better for today.

If you don't install Chipset you may find that you can find and install the HDD and get through textmode and PE stages of setup but will then crash at the third stage of setup, GUI mode. MR smartepants is correct if all you want is mass storage support then you must install the drivers that Mass Storage are dependent on IE Chipset.

You can't put a capstone on a pyramid if you have not built the base first.

Chipset drivers definitely won't be supported in two years. Full focus will be on 7 and maybe 8. Official Microsoft XP support ends in 2014 and most anti-virus support for XP ends in 2015.

That's the problem: downloading your Chipset and MassStorage DriverPack would only cover me for all XP-supported chipsets and mass-storage devices to date and the few in the future. So say in eight years I buy a new motherboard, my XP install disc would be useless because it wouldn't have the AHCI drivers to use the SATA drive in its native mode.

It sounds to me I'm trying to do the impossible, and the best compromise would be to disable AHCI or RAID, or enable IDE emulation mode in the new BIOS before XP setup. This would make the SATA hard disk look and act like a PATA hard disk, allowing XP setup to successfully complete. The only limitation would be I couldn't use any SATA benefits, such as hotplugging, so I'd basically be running a PATA hard disk with thinner cables for improved airflow.

Go to forum: DriverPack Mass Storage

5 Reply by vipejc

(16 replies, posted in DriverPack Mass Storage)

mr_smartepants wrote:

In my opinion, DriverPack Chipset should ALWAYS be included.  This is because it loads the drivers for the motherboard components.  If the drivers for the motherboard components aren't recognized correctly, then the secondary components (sound, LAN, Mass Storage, etc) that connect through the board chipset will also not be recognized correctly.

See, here's my thinking... If I were to create this XP install disc with your most recent version of DriverPack Chipset and MassStorage right now, most or all of the drivers would be useless, especially the chipset drivers, many years into the future and my new motherboard wouldn't support the SATA drive. That's why I'd like to add only generic SATA drivers (Intel and AMD, and AHCI and RAID), because I think SATA drivers that'll work today will work tomorrow for any SATA drive. It's the chipset drivers that vary board to board.

So to be clear, I want to SATA-future-proof an XP install disc for at least the next 20 years. How would you do this?

Go to forum: DriverPack Mass Storage

6 Reply by vipejc

(16 replies, posted in DriverPack Mass Storage)

OverFlow wrote:

You stated that you wanted the widest support possable...

In that case you should add all the main packs... big_smile.
Mass, chipset, LAN, WLAN, Grapihcs and Sound.

Yes, I stated I wanted the widest possible support for SATA drivers. I'm not sure if that includes chipsets? I want to create an XP install disc that'll support any future drivers for Western Digital SATA hard drives.

Go to forum: DriverPack Mass Storage

7 Reply by vipejc

(16 replies, posted in DriverPack Mass Storage)

mr_smartepants wrote:

1) Possibly.  It depends on the preference of the board manufacturer and what "chip-set" they choose.  Most modern boards have the SATA controller built into the "South Bridge" chip or have discrete chips.  So if your main "chip-set" is from Intel, AMD or Nvidia then chances are high that the SATA controller is also from that same OEM.  Other controllers are available (Jmicron, Marvell, HighPoint, etc.)

2) Correct.  The best course of action is to include ZERO drivers with nlite and integrate DriverPacks in your source using DriverPacks BASE.

3) While possible, it's certainly NOT recommended.  Using system files from other OS types is definitely asking for trouble (and possibly illegal).

Do you suggest I download the most recent version of your Chipset DriverPack as well to achieve my goal? Or, is your MassStorage DriverPack all that's needed?

Go to forum: DriverPack Mass Storage

8 Reply by vipejc

(16 replies, posted in DriverPack Mass Storage)

Thanks for your input.

Do motherboards that use AMD processors use the Intel SATA AHCI controller driver, or AMD SATA AHCI controller driver? I could only find the AMD SATA AHCI controller driver for HP notebooks, not desktops, which is what I use. Is this a generic AMD driver, or a driver for a specific chipset or chipsets?

Doesn't your MassStorage DriverPack for XP already include the Intel SATA AHCI Controller Driver, Matrix Storage Manager, and Rapid Storage Technology; and therefore I shouldn't use nLite and only use your DriverPacks BASE to slipstream the drivers into my XP install disc?

Is it possible to download the "ataport.sys" driver and its associated drivers for Vista, and integrate them into the XP install disc as a generic SATA driver, or could this cause an instability?

Go to forum: DriverPack Mass Storage

9 Topic by vipejc

(16 replies, posted in DriverPack Mass Storage)

Hi, I'd like to create an XP Home install disc with the widest possible support for SATA drivers to future-proof the install disc. I don't want drivers for a specific chipset or chipsets.

I'm going to use nLite to create and burn the disc. I use only AMD processors. However, I couldn't find an AMD SATA AHCI controller driver on their site, so I'm assuming since AHCI is an Intel specification, I'll need a generic Intel SATA AHCI controller driver and possibly other drivers. I have the drivers narrowed down to:

Intel SATA AHCI Controller Driver - 7/24/2006, 5.5.0.5135
Intel Matrix Storage Manager - 7/17/2009, 8.9.0.1023
Intel Rapid Storage Technology - 3/23/2010, 9.6.0.1014

Which of the three drivers will I need?
Do the MassStorage DriverPacks for Windows 2000, XP and 2003 include all SATA drivers?
If so, would it be better to download the most recent MassStorage DriverPack for XP to achieve my goal?

Go to forum: DriverPack Mass Storage