(I should know, I wrote it)

and yes it is included in the version of ubcd4win you are useing...

Discs boot fine on Intel x38 (Asus P5E), Intel P35 (Gigabyte GA-P35-DS3R), nVidia NForce 2 (Asus A7N8X-E), and VMWare 6.5.

Chipset plugin isn't used. As far as I know, isn't supported in Bart yet either.

Edit: Drives used in both problem machines are E-machines based. One is a burner, one only a reader. Both are junk. Swapped in my trusty NEC ND-3540 and it booted fine. Thank you for the help!

It boots fine on another system I have with an NForce 2, but on the Intel machine, it doesn't load at all. I get a message right away that says:

INF file txtsetup.sif is corrupt or missing, status 8192.

Do you use the same CD? Then there is a hardware failure.
Bad burned media, difficult to read. Try good qualitiy media and use imgburn.
Half broken CD drive. Half broken RAM. Bad cable. Bad capacitors.

I got a BSOD at 0x7e at a ICH7-M, 8086 27C5, in the meatime too.
UBCD4Win does boot to desktop. There is the BSOD Reading and writing data to hard disk.
Removing  KR10N.sy_ did resolve this. No more BSOD.
There is a driver conflict between KR10N.sy_ and iastor70.sy_

INF file txtsetup.sif is corrupt or missing, status 8192.

The system has the latest BIOS version 0504 and has had it installed for some time now.

Intel D925XCV motherboard. It loads to the desktop background with a working mouse, but after that it blue screens with

STOP: 0x0000007E. (0xC0000005, 0xF7D579EF, 0xF8A6D730, 0xF8A6D42C)

There is a possible driver conflict.
KR10N.sy_ and MegaINTL.sy_ are loaded first, iastor70.sy_ are loaded next.

Try a addon plugin\drivers\bts_addon.inf

[Version]
Signature="$Windows NT$"

[PEBuilder]
Name="Driver: addon PnpInterface"
Enable=1

[DelLine]
;possible conflict iastor70.sy_
"txtsetup.sif", "SCSI.LOAD", "KR10N"
"txtsetup.sif", "SCSI.LOAD", "MegaINTL"

Try updating the BIOS.

i don't belive that the driver is the same in all three packs... but i have not looked yet...

STOP: 0x0000007E. (0xC0000005, 0xF7D579EF, 0xF8A6D730, 0xF8A6D42C)

iastor70.sy_ - Address F7D579EF base at F7D54000, DateStamp 45d0d237

============
RAID Devices
============
PCI\VEN_8086&DEV_2652&SUBSYS_43568086&REV_03\3&11583659&0&FA
    Name: PCI Device
    Hardware ID's:
        PCI\VEN_8086&DEV_2652&SUBSYS_43568086&REV_03
        PCI\VEN_8086&DEV_2652&SUBSYS_43568086
        PCI\VEN_8086&DEV_2652&CC_010601
        PCI\VEN_8086&DEV_2652&CC_0106
    Compatible ID's:
        PCI\VEN_8086&DEV_2652&REV_03
        PCI\VEN_8086&DEV_2652
        PCI\VEN_8086&CC_010601
        PCI\VEN_8086&CC_0106
        PCI\VEN_8086
        PCI\CC_010601
        PCI\CC_0106
PCI\VEN_8086&DEV_266F&SUBSYS_43568086&REV_03\3&11583659&0&F9
    Name: IDE Controller
    Hardware ID's:
        PCI\VEN_8086&DEV_266F&SUBSYS_43568086&REV_03
        PCI\VEN_8086&DEV_266F&SUBSYS_43568086
        PCI\VEN_8086&DEV_266F&CC_01018A
        PCI\VEN_8086&DEV_266F&CC_0101
    Compatible ID's:
        PCI\VEN_8086&DEV_266F&REV_03
        PCI\VEN_8086&DEV_266F
        PCI\VEN_8086&CC_01018A
        PCI\VEN_8086&CC_0101
        PCI\VEN_8086
        PCI\CC_01018A
        PCI\CC_0101
2 matching device(s) found.

I tried using MassStorage 9.01 and 8.05 with the same problem.

I'll help you in any way that I can and I really appreciate all the hard work that goes into a project like yours. Keep it up!