VOGONS


First post, by Sly_Botts

User metadata
Rank Member
Rank
Member

Hi everyone,

So I decided I wanted to retire my Pentium 4 Prescott 3.2Ghz ASUS P4P800X system and try to build a modest 2005 Windows XP system.

CPU: Socket 939 Athlon 64 X2 4200+ Manchester
Motherboard: ASUS A8V-MX
RAM: 1GB DDR1 PC3200 2-3-3-7-10 timings
Sound: Sound Blaster Audigy 2 ZS
Video: ATI Radeon x800 pro 256MB
Storage: WD 250GB SATA III SSD with SATA to IDE Adaptor by StarTech

So I was able to obtain this motherboard from ebay for a fairly expensive price. (65 Euro's plus 35 shipping to Canada). My options were very limited as most Socket 939 Motherboards I could find were PCIe only and those that had an AGP slot were very expensive (Hundreds of Dollars). So i settled for this one despite my fears of it having a VIA chipset.

The attachment A8VMotherboard.jpg is no longer available

Let me tell you, this was quite the time.

First I discovered that the Chipset VIA VT8251 doesn't play well with SATA drives that are not SATA I or II (mostly just SATA I) However it could detect the SSD despite it being SATA III and I was able to get windows XP installed and run it in RAID MODE. AHCI was not recommended for this MB as apparently the chipset was designed to run SATA drives in RAID mode to perform the same function as AHCI. Despite this SSD being detected and useable, it would cause issues while running Windows XP. Files would get deleted or drivers deleted, settings changed etc; Very strange behaviour, so I decided to bypass the SATA controller altogether.

The other issue with this motherboard which killed it for me initially was that there are issues with the 8M800 AGP chipset not being able to handle fast ATI cards and many others. There were some Nvidia cards that would work (See 6600 GT) but I bought this to utilize my x800 pro. So I was determined to make it work as it would crash any time I tried to play a game or run any benchmarks. So here is what I did after 3 days of troubleshooting:

1: Update the Bios: I updated the bios to the latest 0503 bios

2: In the bios I had to make sure my AGP settings were specific:

The attachment AGP.jpg is no longer available

3: I wiped my drives and did a fresh install of XP 32-bit SP3

4: Once XP was installed I installed the VIA 4in1 chipset ver.456, followed by ver.524a. Right after this I went into device manager, found the VIA CPU-AGP controller and made sure the driver was updated to VIA CPU to AGP2.0/AGP3.0 Controller

5: Installed AMD Dual-Core Optimizer patch for XP and the AMD K8 processor drivers for the X2

6: Installed .Net frameworks and drivers for Sound Blaster AUdigy.

7: Finally installed Catalyst 5.13 for the x800pro.

8: System reboots, it automatically turns off AGP Read, AGP Write, PCI Read and PCI write because of SmartGart.

9: Turn on AGP Read, AGP Write, reboot.

10: Turn on PCI Read, PCI write, reboot.

Enjoy Games.

On a side note: After all this, I am noticing some chirping on the sound card when I'm playing games or music. I'm going to look into this.

*UPDATE*
I was unable to fix the "chirping" issue using the George Breese VIA PCI Latency Patch, so I opted to use a non Creative card in Windows XP

However I was able to get this system to also run windows 98se without issues, using the Audigy 2 sz. I guess there must be something with the way XP handles PCI buses, I don't know but the Audigy runs great in win98 and will even emulate an SB16 so a good number of DOS games will work. Unfortunately my motherboard doesn't work with SB16 emulation in DOS with the Audigy2 even with the patch.

AMD Athlon 64 X2 4200+ 2.2Ghz (AGP ASUS A8VMX WINXP)

3dMark 2000: 19433

3dMark 2001: 27092

3dMark 2003: 14532

3dMark 2005: 6569

3dMark 2006: 2615

AMD Athlon 64 X2 4200+ 2.2Ghz (AGP ASUS A8VMX WIN98 SE)

3dMark 1999: 24829

3dMark 2000: 20520

3dMark 2001: 18128

3dMark 2003: 12079

Last edited by Sly_Botts on 2026-09-25, 20:47. Edited 4 times in total.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 1 of 29, by shevalier

User metadata
Rank Oldbie
Rank
Oldbie
Sly_Botts wrote on 2026-09-06, 04:01:

On a side note: After all this, I am noticing some chirping on the sound card when I'm playing games or music. I'm going to look into this.

turn on AGP delayed transaction and PCI delayed transaction in the BIOS setup.

Aopen MX3S, PIII-S Tualatin 1133, Radeon 9800Pro@XT BIOS, Audigy 4 SB0610
JetWay K8T8AS, Athlon DH-E6 3000+, Radeon HD2600Pro AGP, Audigy 2 Value SB0400
Gigabyte Ga-k8n51gmf, Turion64 ML-30@2.2GHz , Radeon X800GTO PL16, Diamond monster sound MX300

Reply 2 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member
shevalier wrote on 2026-09-06, 05:31:
Sly_Botts wrote on 2026-09-06, 04:01:

On a side note: After all this, I am noticing some chirping on the sound card when I'm playing games or music. I'm going to look into this.

turn on AGP delayed transaction and PCI delayed transaction in the BIOS setup.

Yeah unfortunately there's no option in the bios I'll probably just move the card to a slot farther away from the GPU and CPU. Micro ATX board so that's probably why.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 3 of 29, by shevalier

User metadata
Rank Oldbie
Rank
Oldbie
Sly_Botts wrote on 2026-09-06, 14:34:
shevalier wrote on 2026-09-06, 05:31:
Sly_Botts wrote on 2026-09-06, 04:01:

On a side note: After all this, I am noticing some chirping on the sound card when I'm playing games or music. I'm going to look into this.

turn on AGP delayed transaction and PCI delayed transaction in the BIOS setup.

Yeah unfortunately there's no option in the bios I'll probably just move the card to a slot farther away from the GPU and CPU. Micro ATX board so that's probably why.

Bad.
The most standard BIOS option for VIA.
Helps a lot when two low-latency drivers start fighting for access.
Besides, if the graphics card has its own memory, the sound card definitely doesn't.
And it's time to play the sample.

Aopen MX3S, PIII-S Tualatin 1133, Radeon 9800Pro@XT BIOS, Audigy 4 SB0610
JetWay K8T8AS, Athlon DH-E6 3000+, Radeon HD2600Pro AGP, Audigy 2 Value SB0400
Gigabyte Ga-k8n51gmf, Turion64 ML-30@2.2GHz , Radeon X800GTO PL16, Diamond monster sound MX300

Reply 4 of 29, by Towncivilian

User metadata
Rank Newbie
Rank
Newbie

I have a very similar A8V Deluxe motherboard. It also behaves strangely with SSDs using its onboard SATA controller and also the AGP bus is finicky too. I dislike this board to be honest.

I'm wondering if the aforementioned AGP & PCI Delayed Transaction BIOS options are present but for some reason hidden, and could be enabled via modification?

abit BX-133 RAID, P3-S 1.4Ghz, 768MB PC133, Radeon 9000 PRO, AWE64, 2x40GB RAID1, Sony SDT-9000 & Connor CTD-8000 SCSI DDS2 DAT drives, Realtek 8169 1GB NIC, Adaptec DuoConnect AUA-3121, Win2k SP4
Depeche Mode Live Wiki

Reply 5 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member
shevalier wrote on 2026-09-06, 18:56:
Bad. The most standard BIOS option for VIA. Helps a lot when two low-latency drivers start fighting for access. Besides, if the […]
Show full quote
Sly_Botts wrote on 2026-09-06, 14:34:
shevalier wrote on 2026-09-06, 05:31:

turn on AGP delayed transaction and PCI delayed transaction in the BIOS setup.

Yeah unfortunately there's no option in the bios I'll probably just move the card to a slot farther away from the GPU and CPU. Micro ATX board so that's probably why.

Bad.
The most standard BIOS option for VIA.
Helps a lot when two low-latency drivers start fighting for access.
Besides, if the graphics card has its own memory, the sound card definitely doesn't.
And it's time to play the sample.

*removed comment as I was incorrect*

Last edited by Sly_Botts on 2026-09-16, 20:53. Edited 1 time in total.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 6 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member
Sly_Botts wrote on 2026-09-06, 04:01:
Hi everyone, […]
Show full quote

Hi everyone,

So I decided I wanted to retire my Pentium 4 Prescott 3.2Ghz ASUS P4P800X system and try to build a modest 2005 Windows XP system.

CPU: Socket 939 Athlon 64 X2 4200+ Manchester
Motherboard: ASUS A8V-MX
RAM: 1GB DDR1 PC3200 2-3-3-7-10 timings
Sound: Sound Blaster Audigy 2 ZS
Video: ATI Radeon x800 pro 256MB
Storage: WD 250GB SATA III SSD with SATA to IDE Adaptor by StarTech

So I was able to obtain this motherboard from ebay for a fairly expensive price. (65 Euro's plus 35 shipping to Canada). My options were very limited as most Socket 939 Motherboards I could find were PCIe only and those that had an AGP slot were very expensive (Hundreds of Dollars). So i settled for this one despite my fears of it having a VIA chipset.

The attachment A8VMotherboard.jpg is no longer available

Let me tell you, this was quite the time.

First I discovered that the Chipset VIA VT8251 doesn't play well with SATA drives that are not SATA I or II (mostly just SATA I) However it could detect the SSD despite it being SATA III and I was able to get windows XP installed and run it in RAID MODE. AHCI was not recommended for this MB as apparently the chipset was designed to run SATA drives in RAID mode to perform the same function as AHCI. Despite this SSD being detected and useable, it would cause issues while running Windows XP. Files would get deleted or drivers deleted, settings changed etc; Very strange behaviour, so I decided to bypass the SATA controller altogether.

The other issue with this motherboard which killed it for me initially was that there are issues with the 8M800 AGP chipset not being able to handle fast ATI cards and many others. There were some Nvidia cards that would work (See 6600 GT) but I bought this to utilize my x800 pro. So I was determined to make it work as it would crash any time I tried to play a game or run any benchmarks. So here is what I did after 3 days of troubleshooting:

1: Update the Bios: I updated the bios to the latest 0503 bios

2: In the bios I had to make sure my AGP settings were specific:

The attachment AGP.jpg is no longer available

3: I wiped my drives and did a fresh install of XP 32-bit SP3

4: Once XP was installed I installed the VIA 4in1 chipset ver.456, followed by ver.524a. Right after this I went into device manager, found the VIA CPU-AGP controller and made sure the driver was updated to VIA CPU to AGP2.0/AGP3.0 Controller

5: Installed AMD Dual-Core Optimizer patch for XP and the AMD K8 processor drivers for the X2

6: Installed .Net frameworks and drivers for Sound Blaster AUdigy.

7: Finally installed Catalyst 5.13 for the x800pro.

8: System reboots, it automatically turns off AGP Read, AGP Write, PCI Read and PCI write because of SmartGart.

9: Turn on AGP Read, AGP Write, reboot.

10: Turn on PCI Read, PCI write, reboot.

Enjoy Games.

On a side note: After all this, I am noticing some chirping on the sound card when I'm playing games or music. I'm going to look into this.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 7 of 29, by shevalier

User metadata
Rank Oldbie
Rank
Oldbie
Sly_Botts wrote on 2026-09-07, 04:46:
shevalier wrote on 2026-09-06, 18:56:
Bad. The most standard BIOS option for VIA. Helps a lot when two low-latency drivers start fighting for access. Besides, if the […]
Show full quote
Sly_Botts wrote on 2026-09-06, 14:34:

Yeah unfortunately there's no option in the bios I'll probably just move the card to a slot farther away from the GPU and CPU. Micro ATX board so that's probably why.

Bad.
The most standard BIOS option for VIA.
Helps a lot when two low-latency drivers start fighting for access.
Besides, if the graphics card has its own memory, the sound card definitely doesn't.
And it's time to play the sample.

I fixed it!!!

I had to install the George Breese VIA PCI Latency Patch.

Enabled PCI Delay Transaction in the VT8235 southbridge, to smooth out video capture cards when Athlon CPU cooling is enabled.

The ‘delayed transaction’ option in the BIOS reduces performance by a catastrophic 0.5–1%. 😀
Something Asus, in its battle against common sense, could never bring itself to do.

Aopen MX3S, PIII-S Tualatin 1133, Radeon 9800Pro@XT BIOS, Audigy 4 SB0610
JetWay K8T8AS, Athlon DH-E6 3000+, Radeon HD2600Pro AGP, Audigy 2 Value SB0400
Gigabyte Ga-k8n51gmf, Turion64 ML-30@2.2GHz , Radeon X800GTO PL16, Diamond monster sound MX300

Reply 8 of 29, by momaka

User metadata
Rank Oldbie
Rank
Oldbie

Wow, so much good info here!
Thank you for sharing your troubleshooting experience and steps to resolve the issues, Sly_Botts. 😀

I have an ASUS A8V-MX as well that I bought over a decade ago just because it was super cheap on eBay and listed as not working / for parts or repair.
It ended up working, but just needed 1 electrolytic cap changed (the board uses Matsushita FJ/FJS which are known good series, but there was one failed one for no particular reason.)
Anyways, good to have this info if/when I get to do a build with it. Or I might sell it, now that you mention how crazy the prices have gone on these. FWIW, I got mine for $5 back then. Shipping was something like $15, but that's because I also ended up buying another s939 board from the same seller and had the shipping combined. On a 2nd thought, I'll probably end up keeping it, since this is my only s939 board with true AGP. I do have two 939Dual-SATA2 boards, but GPU-Z always reports the AGP bus as "AGP 1x @ PCI"... so not sure if it's a true AGP bus. Plus, one of them is on its way out (dying Southbridge.)

One thing I remember about the A8V-MX back when I did a temporary setup with it (in order to test it) was that it doesn't seem to be capable of any CPU overclocking. Basically, any time I tried to increase the bus speed, even by 1 MHz, the board would not boot anymore and needed a CMOS reset. Curious if that's the case with yours too. I have a lot of 3200+ Venice CPUs and most of them seem to have no problem running at 2.5-2.6 GHz (a +25% OC) on stock voltage, which is basically about on par with the 4000+ (which runs at 2.4 GHz, but has twice the L2 cache). One of these OC'ed on this board and with an older AGP video card (like a GeForce 4 or FX 5000 series) could make for a really nice Windows 98 retro rocket, I think.

BTW, for anyone curious, I did a "cap map" and rough power rail map-out for this board, which can be seen here:
https://www.badcaps.net/filedata/fetch?id=2200556

Reply 9 of 29, by Towncivilian

User metadata
Rank Newbie
Rank
Newbie

Thanks for posting that VIA driver patch link, that's fantastic because my primary intended purpose for this computer is for video capture of VHS using specific ATI All-in-Wonder graphics cards that have S-Video input. I will apply the patch for good measure.

My A8V-Deluxe has an Opteron 165. I think I had some mild success with overclocking it, but don't remember exactly where it landed. I know it was unable to reach the phenomenal 50% overclock to 2.4ghz (from stock 1.8ghz) that my DFI LanParty NF4 Ultra-D achieved 20 years ago... how time flies.

abit BX-133 RAID, P3-S 1.4Ghz, 768MB PC133, Radeon 9000 PRO, AWE64, 2x40GB RAID1, Sony SDT-9000 & Connor CTD-8000 SCSI DDS2 DAT drives, Realtek 8169 1GB NIC, Adaptec DuoConnect AUA-3121, Win2k SP4
Depeche Mode Live Wiki

Reply 10 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member

Err I was jumping the gun. The patch only worked for a short period and then the chirping came back. I'm going to have to completely abandon using an audigy on the motherboard. I might have to just use the integrated audio or try my enoniq audio PCI 1370. It just boils down to the card being hungry for bandwidth on the PCI Lane.

On another note I was able to overclock this motherboard to post at 2.4 GHz from 2.2 GHz with the Athlon 64 X2 4200 plus. Despite not being able to adjust the voltage. However it did freeze during a CPU test in 3D Mark 05. But to get the overclock I had to set the motherboard frequency to 218 MHz and the HT to 600mhz. The ram 166 MHz cl 2-3-4-7-10 1t. The ram has no issues but I don't think this motherboard likes when you overclock the CPU for some reason. If I was able to increase the voltage I don't think I'd have a problem but there's no option here. I also think this is one of those motherboards that overclock the PCI and AGP slots when you overclock the CPU despite setting the frequency manually. I was able to get that CPU up to 2.6 gigahertz on a Foxconn motherboard.

Anyway I'm going to try my audio PCI card and if it works good I'll move on to installing Windows 98 and then Dos 6.22. I'll see if I can make this a triple OS retro gaming system.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 11 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member

Looks like the ES1370 ran flawlessly. This might work to my advantage. I'm going to install windows 98 on this system on my 40GB IDE drive and get that going to see if I can use this as a fast windows 98 system. (I already have a P3 1GHZ Voodoo3 system) but Id like to try this out.

I'm also going to use my SD to IDE card adaptor with a 4GB card to try out DOS 6.22. Since this soundcard is support in DOS and since I already have windows 3.1 installed on the SD card I can use that to run the installer and get this card working in DOS. Yeah I know the OPL emulation sucks but the 8MB wavetable is really really really nice on this card for DOS games.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 12 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member

I did end up getting Windows 98 installed on this motherboard and the Sound Blaster Audigy 2 Zs ran flawlessly. However I think this is because the nature of how the drivers in Windows 98 work VS Windows XP (VxD vs WDM) and how Windows 98 itself handles the way the hardware communicates. The WDM drivers in windows XP being slower gives just enough time for a delay to the Audigy (Which is a BUS HOG) leading to the chirping etc;. The video driver I used in Win 98 is a Catalyst 6.2 final cut down version designed for Windows 98/me and uses the old control centre.

Final thoughts:

The Asus A8V-MX is a budget Micro-ATX board and I think ASUS was being really cheap trying to save pennies on the dollar with its design. Yes it has an AGP slot and yes you can game on it, but any hardware that is "aggressive" doesn't play well on this mobo in Windows XP. You really have to install things in a specific way and use very specific drivers. (I had to use Catalyst 5.13 in XP, in order for the X800 pro to run stable). I think the idea was to get a cheap motherboard out there to meet basic needs for people or businesses. Although I was able to get this to game in Windows XP, this is definitely not a motherboard I would choose for a retro gaming system unless you want to run windows 98se with an Athlon 64 CPU. A lower tier-mid range card would be fine on here.

I am satisfied that I was able to get it working and gaming in Windows XP, and it will meet my needs for a period based system. I am however very disappointed that I can't use any creative cards in XP which is part of the charm of this era (Ie; EAX). I wish I had known this before I spent too much money on this. If I could I would just go and buy another one but prices being what they are now, even for junk like this...

Phil recently posted about how companies are buying up old hardware, sitting on it and selling it at premiums for people like us. Its too bad really, but a sign of the times.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 13 of 29, by Mister No

User metadata
Rank Newbie
Rank
Newbie
Sly_Botts wrote on 2026-09-06, 04:01:

...
First I discovered that the Chipset VIA VT8251 doesn't play well with SATA drives that are not SATA I or II (mostly just SATA I) However it could detect the SSD despite it being SATA III and I was able to get windows XP installed and run it in RAID MODE. AHCI was not recommended for this MB as apparently the chipset was designed to run SATA drives in RAID mode to perform the same function as AHCI. Despite this SSD being detected and useable, it would cause issues while running Windows XP. Files would get deleted or drivers deleted, settings changed etc; Very strange behaviour, so I decided to bypass the SATA controller altogether.

The issues with SSDs you describe are a perfect example of SATA corruption caused by too high PCI clock. VIA VT8251 works without problems with SSDs if your FSB is set to 200 MHz. Asus A8V-X and A8V-MX don't have a working AGP/PCI lock and therefore require a lot of tinkering to make them stable when overclocking. Stability when overclocking could be achieved by using IDE drives instead of SATA drives (IDE drives are to some degree more tolerant to overclocked PCI bus) or by connecting SATA drives to some of the PCI SATA controllers that are more tolerant to the PCI bus frequency higher than 33 MHz. In any case, you will be limited to the max FSB of around 220 MHZ.

If you still use your motherboard, check the SSDs without overclocking the FSB - they should work just fine.

Reply 14 of 29, by Mister No

User metadata
Rank Newbie
Rank
Newbie
momaka wrote on 2026-09-07, 09:45:

...
I do have two 939Dual-SATA2 boards, but GPU-Z always reports the AGP bus as "AGP 1x @ PCI"... so not sure if it's a true AGP bus. Plus, one of them is on its way out (dying Southbridge.)

939Dual-SATA2 definitely has *true* AGP bus, I tested it with 1950GT AGP, 2600XT AGP, 3850 AGP, 6800LE AGP and 7600GT AGP. All work without problems at AGP 8x (although I keep the bridged Rialto cards at AGP 4x for longevity reasons). This "AGP 1x @ PCI" you got is very strange, something must be wrong with your Windows installation or maybe with missing/corrupt drivers. I have never seen this problem on 939Dual-SATA2 - not on WinXP SP3, Win7 x32 or Win7 x64.

Something similar ("AGP 8x@PCI") can be seen on nForce3 boards when GART driver si missing in Windows 7 X64.

Reply 15 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member
Mister No wrote on 2026-09-17, 22:08:
Sly_Botts wrote on 2026-09-06, 04:01:

...
First I discovered that the Chipset VIA VT8251 doesn't play well with SATA drives that are not SATA I or II (mostly just SATA I) However it could detect the SSD despite it being SATA III and I was able to get windows XP installed and run it in RAID MODE. AHCI was not recommended for this MB as apparently the chipset was designed to run SATA drives in RAID mode to perform the same function as AHCI. Despite this SSD being detected and useable, it would cause issues while running Windows XP. Files would get deleted or drivers deleted, settings changed etc; Very strange behaviour, so I decided to bypass the SATA controller altogether.

The issues with SSDs you describe are a perfect example of SATA corruption caused by too high PCI clock. VIA VT8251 works without problems with SSDs if your FSB is set to 200 MHz. Asus A8V-X and A8V-MX don't have a working AGP/PCI lock and therefore require a lot of tinkering to make them stable when overclocking. Stability when overclocking could be achieved by using IDE drives instead of SATA drives (IDE drives are to some degree more tolerant to overclocked PCI bus) or by connecting SATA drives to some of the PCI SATA controllers that are more tolerant to the PCI bus frequency higher than 33 MHz. In any case, you will be limited to the max FSB of around 220 MHZ.

If you still use your motherboard, check the SSDs without overclocking the FSB - they should work just fine.

Yeah unfortunately this mobo's pci bus is tied to the cpu and increases in frequency when you overclock (synchronized clock architecture), So in order to do what you suggest I'd have to under clock the CPU. I wasn't overclocking when I was having issues with the SATA drives. This in particular motherboard just doesn't play well with SATA drives. My Asus p4p800-x on the other hand had no issues.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 16 of 29, by Dothan Burger

User metadata
Rank Member
Rank
Member
Sly_Botts wrote on 2026-09-16, 20:47:

Phil recently posted about how companies are buying up old hardware, sitting on it and selling it at premiums for people like us. Its too bad really, but a sign of the times.

IMHO if a VIA board doesn't play nice in DOS it's up for sale, they have too many flaws to put up with that. The fact that prices are high may work in your favor, crack somebody else's head. You already have a working system to post pictures to Ebay.

Reply 17 of 29, by Sly_Botts

User metadata
Rank Member
Rank
Member
Dothan Burger wrote on 2026-09-18, 02:49:
Sly_Botts wrote on 2026-09-16, 20:47:

Phil recently posted about how companies are buying up old hardware, sitting on it and selling it at premiums for people like us. Its too bad really, but a sign of the times.

IMHO if a VIA board doesn't play nice in DOS it's up for sale, they have too many flaws to put up with that. The fact that prices are high may work in your favor, crack somebody else's head. You already have a working system to post pictures to Ebay.

Yeah sb16 emulation in pure DOS usually fails on some Socket 939 boards because the BIOS lacks DDMA / PC/PCI support required by the Creative drivers in pure DOS. My ensoniq audio 1370 fails to emulate in both windows 98 and dos because of this.

It is possible to commit no errors and still lose. That is not a weakness, that is life.

Reply 18 of 29, by Dothan Burger

User metadata
Rank Member
Rank
Member
Sly_Botts wrote on 2026-09-18, 04:09:
Dothan Burger wrote on 2026-09-18, 02:49:
Sly_Botts wrote on 2026-09-16, 20:47:

Phil recently posted about how companies are buying up old hardware, sitting on it and selling it at premiums for people like us. Its too bad really, but a sign of the times.

IMHO if a VIA board doesn't play nice in DOS it's up for sale, they have too many flaws to put up with that. The fact that prices are high may work in your favor, crack somebody else's head. You already have a working system to post pictures to Ebay.

Yeah sb16 emulation in pure DOS usually fails on some Socket 939 boards because the BIOS lacks DDMA / PC/PCI support required by the Creative drivers in pure DOS. My ensoniq audio 1370 fails to emulate in both windows 98 and dos because of this.

Didn't know 939 boards had that problem, I assumed the whole point in bothering with VIA was to get DOS support or at least SB emulation in windows. That sucks because it should've been a killer setup.

Reply 19 of 29, by Mister No

User metadata
Rank Newbie
Rank
Newbie
Sly_Botts wrote on 2026-09-18, 01:39:

Yeah unfortunately this mobo's pci bus is tied to the cpu and increases in frequency when you overclock (synchronized clock architecture), So in order to do what you suggest I'd have to under clock the CPU. I wasn't overclocking when I was having issues with the SATA drives. This in particular motherboard just doesn't play well with SATA drives. My Asus p4p800-x on the other hand had no issues.

I think that we misunderstood each other, what I'm suggesting is to leave the FSB at 200 MHz and therefore run the CPU at default speed. No underclocking or overclocking.

VIA VT8251 can definitely work reliably with SSDs, I had no problems, but I was using AHCI mode. And I kept the FSB at 200 MHZ, AGP at 66MHz and PCI at 33 MHz.