been struggling with a Slot 370 motherboard's usb controller freezing win9x

[chrisNova777]

so i thought i would enlist the help of some AI:

if its a known bug is there a known solution to the problem of the usb 1.1 controller freezing win9x on a FP-SI630E motherboard

and it turns out:::

Yes, the USB controller freeze on the Future Power FP-SI630E (and similar SiS 630/730 chipset boards) is a well-known legacy quirk in Windows 9x.

The issue stems from a hardware/driver conflict between the integrated SiS 7001 OHCI USB host controller and Windows 9x IRQ steering or ACPI power management. The motherboard's BIOS often assigns the USB host controller an IRQ that conflicts with PCI steering or APM (Advanced Power Management), causing Windows 95/98/SE to lock up completely during boot or as soon as a USB driver initializes.

Depending on whether you need USB support from the onboard ports, there are several standard workarounds:

Solution 1: Disabling Onboard USB & Using a PCI USB Card (Most Reliable)
Because the SiS 7001 controller integrated into the SiS 630 chipset is notoriously picky under Windows 9x, the most bulletproof, long-term fix used in retro computing is bypassing it entirely:

Enter the BIOS Setup at startup (usually pressing Del).

Go to Integrated Peripherals (or Chipset Features).

Set Onboard USB Controller (or SiS USB Device) to Disabled.

Install a cheap NEC- or VIA-chipset PCI USB 2.0 expansion card. Windows 9x works much more reliably with PCI USB cards, and you get USB 2.0 speeds instead of legacy USB 1.1.

Solution 2: Resolving the IRQ & ACPI/APM Conflict (To Keep Onboard USB)
If you want to use the native motherboard ports, you must resolve the resource collision:

Disable ACPI / APM in BIOS:

In BIOS, locate power management settings and set ACPI Function to Disabled or switch power management from ACPI to standard APM/Legacy. SiS 630 boards frequently misallocate IRQs to USB when ACPI tables are loaded by Win9x.

Reassign or Reserve IRQs:

In BIOS under PnP/PCI Configurations, ensure Resources Controlled By is set to Auto or manual.

Make sure Assign IRQ for USB is set to Enabled.

If Windows freezes upon loading, manually force the USB controller to an unshared IRQ (such as IRQ 5, 9, or 11) in BIOS or Device Manager.

Safe Mode Cleanup:

Boot Windows 9x into Safe Mode.

Open Device Manager (Control Panel -> System -> Device Manager).

Expand Universal Serial Bus controllers.

Delete all listed USB Root Hubs and SiS 7001 PCI to USB Open Host Controllers.

Expand System Devices and remove any duplicate IRQ Steering entries. 
Experts Exchange

Reboot and allow Windows to re-detect the host controller.

Solution 3: Official SiS Chipset Drivers & USB Supplement
Ensure you are not relying solely on the default Windows 98/98SE generic USB driver:

Windows 95: Requires USB Supplement (USBSUPP.EXE / DETACH.EXE / USBUPD2.EXE) installed before the driver will work. 
VOGONS

SiS AGP/Chipset Driver Pack: Install the official SiS 630 AGP/System driver package (ver. 1.07 or later for Win9x). Installing the proper SiS System Driver helps properly route the internal PCI bus bridges so the USB controller does not crash the OS when initialized. 
VOGONS

If you are using NUSB (Native USB Disk Driver for Win98SE), install the official chipset drivers before applying NUSB, as NUSB will trigger a hard crash if the underlying OHCI host driver isn't properly routed.

[chrisNova777]

do i have to reinstall to disable ACPI?

No, a full drive format isn't strictly required, but simply changing the BIOS toggle on an existing installation will usually cause Windows 9x to hang at boot or throw protection errors because its system device tree is already bound to ACPI. 

To transition from ACPI to APM/Legacy power management without wiping your drive, use one of the following methods:

Option 1: In-Place Overlay Reinstall (Most Reliable Non-Format)

Step 1. Boot to DOS or open a command prompt.
Step 2. Run Setup with the explicit non-ACPI switch: SETUP.EXE /p i
Step 3. The /p i flag forces Windows 9x to skip ACPI hardware detection and construct an APM/PnP BIOS hardware layer instead.

Option 2: Registry and Device Manager Driver Swap

Step 1. Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Detect
Step 2. Create a DWORD value named ACPIOption and set its value to 2 (tells Windows to disable ACPI detection).
Step 3. Open Device Manager, expand System Devices, right-click ACPI BIOS, click Update Driver, choose to pick from a list of hardware, and change the driver to Plug and Play BIOS.
Step 4. Shut down, change your BIOS setting to disable ACPI / enable APM, and restart. Windows will run a full Plug-and-Play hardware scan and reallocate your IRQs.

Option 3: Clean Format & Reinstall (Best for SiS Chipsets)

Step 1. Back up any critical retro files, software, or drivers.
Step 2. Disable ACPI / enable APM in your BIOS before booting the installation media.
Step 3. Format and clean install—this guarantees no legacy ACPI registry keys remain on SiS 630 boards to mess with IRQ routing.

[chrisNova777]

The **ACPI (Advanced Configuration and Power Interface)** specification was first published in **December 1996** by Intel, Microsoft, and Toshiba (later joined by HP and Phoenix).

Its OS rollout happened in stages over the late 1990s:

* **Windows 98 (June 1998):** The first mainstream operating system to ship with ACPI support, though early BIOS implementations were notorious for causing stability issues.
* **Windows 2000 (February 2000):** Marked the first fully stable, widespread adoption of OS-controlled power management and hardware configuration.
* **Linux (Early 2000s):** Basic support arrived in the late 2.4 kernel branch, with robust, default ACPI support rolling out with the 2.6 kernel series in late 2003.

ACPI was designed to shift motherboard control, thermal management, and device power states (such as $S3$ sleep and $S5$ soft-off) out of the legacy PC BIOS and directly into the operating system.

When ACPI rolled out during the Windows 98 and Windows 2000 era, it caused major headaches for audio hardware, MIDI interfaces, and DAW performance.

Real-time digital audio requires low, predictable latency without interruptions. ACPI disrupted this workflow in four primary ways:

**1. IRQ Sharing and Routing Conflicts**
Before ACPI, PCI sound cards and MIDI interfaces often required dedicated Hardware IRQs (Interrupt Request lines) to process stream buffers without interruption.

ACPI introduced IRQ Steering. Under Windows 2000/XP’s ACPI HAL, the system grouped almost all PCI devices, USB controllers, and internal components onto a single shared Virtual IRQ (often IRQ 9 or IRQ 11).
* **The Problem:** If a PCI sound card shared an IRQ with a graphics card or a network card, any heavy display redraw or network activity triggered an IRQ flood.
* **The Result:** The CPU paused the audio buffer to service the other device's interrupt, leading to immediate clicks, pops, and buffer underruns in DAWs.

**2. DPC Latency Spikes (Deferred Procedure Calls)**
ACPI hands high-priority hardware execution control to system drivers via Deferred Procedure Calls (DPCs).
* When ACPI queries system health, manages thermal throttling, or checks power status, `ACPI.sys` can hold the CPU locked in a high-priority DPC state for several milliseconds.
* Because audio buffer sizes at low latency (e.g., 64 or 128 samples) require the CPU to return to the audio thread every 1.3 to 2.9 milliseconds, a single long `ACPI.sys` DPC call causes the audio buffer to empty completely before the DAW gets control back.

**3. CPU SpeedStepping and Power States**
ACPI introduced dynamic power management, allowing CPUs to throttle clock speeds (C-states and P-states) to save power and lower temperatures.
* When a CPU drops down to a lower power state, its clock frequency changes instantly.
* The brief latency penalty incurred when the CPU ramps back up to handle a sudden burst of audio processing causes real-time processing dropouts.
* For MIDI, these variable clock cycles degraded timestamp precision, causing noticeable MIDI timing jitter (notes drifting off the grid).

**4. Flaky Early BIOS ACPI Tables**
In the late 1990s and early 2000s, motherboard manufacturers routinely shipped bug-ridden ACPI BIOS tables. Windows depended entirely on these tables to route hardware signals. Poorly written BIOS code frequently misallocated memory ranges or locked up PCI buses during power state transitions, disproportionately impacting high-bandwidth audio interfaces and legacy ISA/PCI MIDI gear.

---

**The Workaround Era ("Standard PC" HAL)**
To bypass these issues, pro audio technicians routinely forced Windows 2000 and Windows XP to install using the **Standard PC HAL** instead of the ACPI HAL.

By hitting F5 or F6 during Windows setup and selecting "Standard PC," users disabled ACPI entirely. This allowed manual assignment of dedicated IRQs to PCI slots in the BIOS, completely eliminating shared IRQ latency conflicts at the cost of losing automatic power-off and sleep features.

[chrisNova777]

wow now the motehrboard just stopped booting up... some retro hardware is just haunted.. time to throw this one in the bin. SIS 630E chipset can suck it