VOGONS

Search

Common searches

Search results

Display options

Display options

Re: Via C3 Ezra Slot 1 Machine

Posted on 2019-02-18, 00:43

In addition to the re-cap, another potential difference is the MSI MS-6905 Slotket. Tpowell.ca and I are both using v2.0 and you are using v2.3. You mentioned jumpering the slotket to 1.4v. A v2.0 only goes down to 1.5v. I am using a 1.35v CPU. Both the 1.5v and auto settings have the same stability …

Re: Problems with Media Vision PAS16P

Posted on 2019-02-13, 19:48

This is an interesting card. I've never seen a PAS16P that is missing the LMSI connector and controller chip before. Almost like a PAS16LL. I agree that the -5v rail is the likely issue, but these cards are also speed sensitive and will have problems if you are trying to use them in anything faster …

Re: PAS16 revived!

Posted on 2019-02-12, 19:49

Good work. I have a couple of PAS16s as well, though I'm not currently using one in anything. They are good cards if you are looking to stray off the beaten path a bit yet still have something very usable. Good quality hardware/software package, many of the major games from the time natively support …

Re: Via C3 Ezra Slot 1 Machine

Posted on 2019-02-09, 21:31

So, everyone having issues with 133MHz FSB - is your VIA C3 actually rated at 100MHz or 133MHz? This is something else to consider because you can have variants rated at both FSBs for a given rated CPU speed, and 133MHz FSB can be unstable for a 100MHz rated CPU. You can check the rating by looking …

Re: Via C3 Ezra Slot 1 Machine

Posted on 2019-02-08, 15:31

I can run Rayer's FSB tool all day as long as I keep the FSB below 133MHz and above whatever combination with the multiplier keeps the CPU at or above 200MHz. Tenorman. For sound, I gave up on my SB32/AWE32 since it lacked crucial SBPro compatibility and lets be honest, if you have a proper MT-32 …

Re: Via C3 Ezra Slot 1 Machine

Posted on 2019-02-07, 17:12

Past week my GA-6BXC is having some issues with Rayers FSB tool for DOS in combination with VIA (Nehemiah) processors. Intel CPU works fine with this tool though. Well, this motherboard was used for lots of experiments already. I've noticed that if I mess with this utility too much on my system, it …

Re: Via C3 Ezra Slot 1 Machine

Posted on 2019-02-07, 17:00

If I can find some time I will see if my recapped GA-6BXC does 133MHz FSB for multiple hours without errors. In the past it always did 133MHz without issues, but it was not like it was set at 133MHz by default. I know that this doesn't necessary mean anything, but I have been through two different …

Re: Via C3 Ezra Slot 1 Machine

Posted on 2019-02-07, 14:51

Its remarkable how close our setups are. Well, lots of things are different, but it is funny how we both arrived on the same motherboard, BIOS, Ezra CPU, slotket, and an NVidia + Voodoo 2 combo. Things get pretty different when it comes to storage and sound. What is the stepping code on your CPU? I …

Re: Via C3 Ezra Slot 1 Machine

Posted on 2019-02-05, 22:50

Hello All, I know this thread is getting old, but I have made some changes over the past month and wanted to do a final update in case someone else is looking to build something similar. -I re-did the OS installations. I found that I was often times re-doing the same stuff (game installations, …

Re: Sound Blaster AWE64 and AWEUTIL in pure DOS

Posted on 2019-01-30, 19:40

That's the trouble with all these 'Install' utilities; they mess up your startup files because they try to solve for all possible contingencies. It's DOS, man! The entire system configuration is just a few short lines of text. It can and should always be done manually. That's how real power users …

Re: Sound Blaster AWE64 and AWEUTIL in pure DOS

Posted on 2019-01-30, 01:11

I had a problem that I solved by taking CTCM out of config.sys and calling it in autoexec.bat as well. I'm curious if you have other PnP hardware that needs to be initialized as well. In my case, I found that order was key, which is why it had be put in autoexec.bat. https://www.vogons.org/viewtopic …

Re: Can't See D: Drive in Win 98 MS-DOS Mode

Posted on 2019-01-30, 01:01

What if you set the drive as active? (PM will still take preference so wont affect booting) I dont think it will make a change but cant hurt to try? Seems really strange that Win98 can see it but dos cant? I don't remember for certain, but I believe I tried that and it didn't help. Yes, this is …

Re: Can't See D: Drive in Win 98 MS-DOS Mode

Posted on 2019-01-25, 00:35

My only goal really is to make sure I have some sort of half way sensible partitioning scheme and enough space for everything (DOS games, Windows, Linux). It doesn't need to all be on one partition. I am using a 32 GB compact flash card. I'm using a Gigabyte GA-6BXC 440BX board with the PowerLeap …

Re: Can't See D: Drive in Win 98 MS-DOS Mode

Posted on 2019-01-23, 17:06

I am almost certain this is being caused by some sort of 8 GB limitation with my BIOS. The version of fdisk that comes with Windows 98 should correctly report sizes up to 64 GB, but it gets cut off at 8 GB on this system. Somehow Linux and Windows 98 in GUI mode know how to deal with this and DOS …

Re: Can't See D: Drive in Win 98 MS-DOS Mode

Posted on 2019-01-22, 22:14

I am thinking that it probably has something to do with the 8 GB Int 13h limit. http://web.inter.nl.net/hcc/J.Steunebrink/bioslim.htm#Int13ext "Last but not least, we need a partition utility capable of creating partitions above the 8 GB boundary which the OS can see. The version of FDISK supplied …

Re: Can't See D: Drive in Win 98 MS-DOS Mode

Posted on 2019-01-22, 21:03

Fdisk shows Disk 1's total disk space is 8033MB, yet the accounted space is much, much higher than that. Just adding the two lettered partitions together exceeds the "total disk space" displayed. Yes, my understanding is that there is an 8 GB limit built into the version of FDISK that comes with …

Re: Can't See D: Drive in Win 98 MS-DOS Mode

Posted on 2019-01-22, 20:41

Note sure if this is of any help, but you could try to load your CD-ROM driver low and/or remove the "/L:E" part. If you don't specify the drive letter, it will try to use the next best one available. I don't think it has to do with the CD-ROM driver. If I don't specify the drive letter, the CD-ROM …

Page 2 of 5

Go to top of page Go to top of page
Close window
Close window