F
Flasherly
Next best thing to the site's DOS utilities, if you've got it. Dunno.
I'd have to check my newest Gigabyte MB if it has a
hot/keyboard>BIOS>routine .
Next best thing to the site's DOS utilities, if you've got it. Dunno.
I'd have to check my newest Gigabyte MB if it has a
hot/keyboard>BIOS>routine .
P
Paul
Searcher7 said:
In that Belarc, the BIOS is dated "05/19/2004", but there is
no release number. You can try correlating the date, with the
BIOS dates from the web site.
If I look at the Oct.12 and Dec.4 pages on the archive...
http://web.archive.org/web/20040701...ded.com/product/Download.jsp?motherboardId=81
the BIOS release jumps from
1.13 (12/16/2003)
to
1.16 (10/14/2004)
Your BIOS could be one of the in-between versions.
*******
You also have the option of looking at the physical
motherboard, and reading the paper label on top of the
BIOS chip. If the BIOS has never been flashed before,
the paper label will still be accurate as to what
revision is present.
Paul
M
Mike Easter
Searcher7 said:
Yes that is the Epia and its BIOS in Belarc says 2004 May 10
The BIOS at the Epia site is
BIOS 1.16 2004/10/14 I0100116.bin (257KB)
The EPIA site has a VGA driver
Integrated VGA 16.94.39.14 2004/11/03 *[Note] Please update
this driver with above latest BIOS v.116* EPIA M VGA Driver for Windows
2000/XP 2kxp.zip (6.66M)
So Epia's 'newest' 2004 Nov VGA driver needs Epia's newest 2004 Oct
BIOS, but your BIOS is 2004 May, if I'm interpreting this correctly.
If whatever your vid problem is were known to be improved by the newer
VGA (which isn't necessarily true), then it would be worth the risk to
upgrade your BIOS.
The method I would use to upgrade the BIOS on your XP system with floppy
support would be to make a floppy boot disk with XP using My Computer/
File/ (select floppy)/ Format (options) Create a MS-DOS startup disk.
I would use that MS-DOS in the manner described in the .pdf for the
flash bios tool and ignore everything in that .pdf that has anything to
do with installing Win98 to make a boot dos floppy.
Here's the Epia site that I'm referring to:
http://www.viaembedded.com/en/products/boards/81/1/EPIA_M_(EOL).html
Use the downloads tab
There is also a manual there dated 2012; also the Via 4in1 drivers which
on that page are dated 2002 have some video function.
I would assume that you already installed such 4in1 drivers using the
Via CD which came with the mobo/unit.
L
Loren Pechtel
Yeah, on boards meant for the enthusiast who builds their own system
you'll often see such features. I haven't seen such recovery stuff on
the average boards, though.
S
Searcher7
Ok. I'm going to try and follow your instructions because they seem simple enough.
But starting on page 6 of that PDF mmanual it gets a little confusing. (They really should have someone from the U.S.A. go over all their printed instructions).
So let's see if I got this right.
1) After I insert a formatted floppy disk, I double click "drdflash", whichis on my desktop in order to create a bootable floppy disk.
2) I then double click "vf-102", which is is on my USB flash drive, and copy whatever it produces to the floppy.
3) I also copy "I0100116" from my USB flash drive to the floppy.
4) When I reboot from the floppy, I type "vf-102.exe", and press "Enter".
5) This will start me at the screen shown on page 6, where I type "1" and press "Enter".
6) Then I type in "bak1.bin" and press "Enter".
7) Then I type "2" and press "Enter".
8) Then I type "I0100116" and press "Enter". (The PDF indicates that I should type in the *original* BIOS file name, but I'm assuming that is incorrect).
9) Then I type "0" and press "Enter".
Then it loses me when it says, "Execute vf-102, with the following command line parameters."
Darren Harris
Staten Island, New York.
P
Patrick
(Confusion) you should have a 'zip' file (that you downloaded) called 'VIA
FlashTool 1.02'
Double click this file and you should see this;
https://www.dropbox.com/s/r8ovh6usj38ji6x/p1.jpg?m
Double click the folder thus shown and you should see this;
https://www.dropbox.com/s/2xr7e1kxghv9tbe/p2.jpg?m
Now copy (only) the file 'vf-102' to the floppy.
Ignore or copy to your Desktop, the PDF file 'VIA_Flash_tool_User_Guide
Correct, the file is actually called "I0100116.bin" which you will see by
the 'DIR'command when you you boot from the floppy.
I'm not sure you need to press "Enter", I suspect the Input line will occur
when you press the '1'
Yes, Your old (previous) BIOS will now be saved to the floppy in case you
want to put it back.
I'm not sure you need to press "Enter", I suspect the Input line will occur
when you press the '2'
Correction; Type "I0100116.bin" and press "Enter"
Wait until it says that it's finished.
I'm not sure you need to press "Enter", I suspect the Input line will occur
when you press the '0'
Then it loses me when it says, "Execute vf-102, with the following
command line parameters."
The command line parameters are so that instead of doing the 1, 2, 0, thing
you could have done;
"vf-102.exe -s bak1.bin -p I0100116.bin -r"
I have only a rough idea as to the -c and -b Command-Line-Parameters. one of
these would have reset all the user parameters in the BIOS to defaults.
At this point the BIOS should have been updated and you can remove the
floppy and boot into the BIOS to check all is well.
S
Searcher7
Ok, that is what I did.
So you are saying that I don't have to do anything else after #9, correct?
BTW. I booted with that floppy and typed in "DIR" and received the following:
http://i290.photobucket.com/albums/ll257/Statenislander/Computer/FloppyDIR_zpsd5310a3d.jpg
Darren Harris
Staten Island,New York.
P
Patrick
Go in to the BIOS and check that all is well and that you can see reference
to the new BIOS update. The new BIOS update is required by the Video-driver
at the VIA site.
Precisely, you see the 2 files that you put there and the others are the DOS
OS files that are normally hidden in XP.
S
Searcher7
Ok. For some reason it appears that even though I "updated" the BIOS version hasn't changed.
Belarc still says it is "BIOS: Award Software International, Inc. 6.00 PG 05/19/2004". (Perhaps I mistakenly downloaded the same version I already have?).
I checked the floppy again and this is what I got:
http://i290.photobucket.com/albums/ll257/Statenislander/Computer/FloppyDIR2_zpsbf0427ca.jpg
Also, for some strange reason, when I go to "Device Manager" and uninstall "VIA/S3G UniChrome IGP", which is under "display Adaptors, my system immediately re-install it. Installing the driver "2kxp" afterwards does nothing.
When I uninstall "VIA AC'97 Enhanced Audio Controller (WDM)", which is under Sound, video and game controllers", the system makes me re-install it before I can install the audio drivers I downloaded also.
Anyway, I'll download the BIOS and try again, but after the BIOS update I assume I'm supposed to install the Windows XP Service Pack first. And then the drivers.("2kxp", "audio", "4in1_v_443", "usb2", "FIR for M", and "Lan for M").
Thanks.
Darren Harris
Staten Island, New York.
M
Mike Easter
I was wondering why you didn't show a graphic of the result of the flash
at the time you showed us a graphic of the floppy files.
I'm speaking of the screens seen in the .pdf accompanying the Via Flash
Tool in the .zip on page 7 which says
BIOS Updated!
Please power off or reset system
The date on the BIOS I'm looking at on the Via Epia page
http://www.viaembedded.com/en/products/boards/81/1/EPIA_M_(EOL).html
BIOS 1.16 2004/10/14 I0100116.bin (257KB)
has an older date by 5 days than yours.
I see the backed up bak1.bin on your floppy.
That backup step is described on p.6 of the .pdf. The next step after
backing up is the flashing which says/chooses
(2) Update BIOS
which leads to p.7 BIOS Updated! Poweroff or reset as described. That
was the graphic I expected to see when you posted the graphic of the
floppy files before backup was done.
Once you are sure you have updated the BIOS, then you would update the
VGA. I would assume that the initial installation would have done all
of that business about the 4 in 1, LAN, audio, USB, and other drivers.
All of those drivers on the Via Epia page are old; I wouldn't replace
all that you have with those drivers. Possibly your current XP drivers
are newer.
We haven't discussed any reason why you should be uninstalling your
audio drivers.
If you are due to update Win, I would definitely do that first. I don't
see why you would need to 're-download' the BIOS .bin. If the user
error were that you only backed up but you didn't update the BIOS, then
that is all you should need to do.
- try to recall if you failed to do the update BIOS step after you did
the backup BIOS step
- if so, use your existing floppy and its files to update the BIOS;
you needn't do the backup step as it is already done
- update your Windows if it is lacking an update
- examine your currently installed drivers such as 4in1 and LAN etc;
it would be my expectation that all of that stuff has already been done
with your initial install
- once you have some kind of confirmation that you have updated the
BIOS, I would update the VGA.
Apparently the .zip file for the VGA which is a 5 meg file is a big
Setup.exe package, so it, the VGA driver, isn't handled with XP's Device
Manager Update or Uninstall function, the .exe does everything for you
like a black box.
P
Paul
Save off the files from the floppy to a safe place.
Make *another* backup copy of the BIOS (call it BAK2.BIN).
See if that backup copy is now the same as BAK1.BIN,
assuming BAK1.BIN was created by making your safety backup
copy of the BIOS.
You will need a means to compare the two files. I use
a checksum program, as a quick means to compare them.
Other means, would be an actual comparison program.
Note that, BIOS files are not "plaintext" by default.
BIOS files are far from monolithic. They're a small file
system. The tools available, don't even do a good job of
taking a BIOS file apart properly.
When a virgin BIOS starts for the first time, the DMI and
ESCD sections of the BIOS get updated. This prevents the
*new* backup copy, from matching byte-for-byte the
I0100116.bin file. So don't expect BAK2.BIN to match
I0100116.bin. But if BAK1.BIN matches BAK2.BIN, then
you know your attempt to flash the BIOS has failed to "take".
*******
So what can we check ?
Does BAK1.bin equal BAK2.bin ? If so, nothing got flashed.
We can't compare checksums on I0100116.bin and BAK2.bin
and expect the files to be the same. I0100116.bin is an
image of a virgin file, while BAK2.bin could contain the
now updated DMI and ESCD segments.
Without showing all the details, you could consider the
BIOS looks like this. I have a tool that handles the
second section.
Boot block
Main BIOS section <--- inside this are eight files
DMI
ESCD
*******
On your BIOS, the main BIOS section breaks down into
individual files. To disassemble the BIOS, I use CTMC10.zip
package from heise (CT magazine).
ftp://ftp.heise.de/pub/ct/ctsi/ctmc10.zip
Amazingly, that download file is still available after all
these years.
Inside the file, the two useful files are "splitawd.exe"
and "lha255e.exe".
The lha255e.exe file is a self-extracting file. I could not
open it with 7ZIP. Place the lha255e.exe file in a *separate* folder.
Execute it, and you should get something like "lha.exe" plus
eight other useless files. Don't move the lha.exe file just
yet.
To take the I0100116.bin file (262144 bytes) apart,
I used "splitawd.exe" and "lha x somefile.lha" type commands.
If you run
splitawd.exe I0100116.bin
it will complain it cannot find lha.exe, but it will
still extract the files from the main portion of the BIOS.
It places the files in a folder $MCTEMP. It will create
the folder for you, and put these files in it.
00000000.bin
00000001.bin
00000002.bin
00000003.bin
00000004.bin
00000005.bin
00000006.bin
00000007.bin
Now, transfer the "lha.exe" file (not the lha255e.exe archive),
into the $MCTEMP folder. Using the "cd" command, change
directories to $MCTEMP. Now you can run commands like this:
cd $MCTEMP
lha x 00000000.bin
lha x 00000001.bin
lha x 00000002.bin
lha x 00000003.bin
lha x 00000004.bin
lha x 00000005.bin
lha x 00000006.bin
lha x 00000007.bin
You get extracted files. This is the BIOS file system,
without the boot block.
I0100116.BIN 131,072 bytes
AWARDEXT.ROM 44,304 bytes
ACPITBL.BIN 12,473 bytes
AWARDBMP.BMP 5,772 bytes
_EN_CODE.BIN 21,712 bytes
AWARDEYT.ROM 19,056 bytes
VPSD.BMP 307,980 bytes
MCLECOMB.ROM 60,416 bytes
Notice that, I0100116.BIN 131,072 bytes has the same
name as the original BIOS download file I0100116.BIN 262,144 bytes.
Be careful, when extracting the eight files in the $MCTEMP
folder, to not have the original I0100116.BIN file present,
because it could get overwritten.
When people use decompression tools, they sometimes
manage to extract I0100116.BIN 131,072 bytes over top
of the original BIOS. Then, when they flash the BIOS,
the flasher tool only has half the byte-count it is
supposed to have. I believe people have bricked their
board, by using that smaller file (i.e. when a BIOS
flasher tool without extensive self-checks is used
for the flashing exercise).
Anyway, I present the above method, using CTMC10 for
Award BIOS, if you're interested in reading actual
English text inside the BIOS. The eight named files
above, are now in plaintext form. Some of the files
contain executable code, and some contain text.
The BMP files are not "standard BMP" and are a
special format (more research required, but I have
managed to view those files in the past). When the
BIOS POST commences, the BMP files display in color
on the BIOS screen (such as the Energy Star logo perhaps).
For example, _EN_CODE.BIN contains English text that
is displayed on the BIOS screen. These are some examples
extracted with my hex editor.
CMOS battery failed
Override enabled - Defaults loaded
An Energy Star Ally
Press F1 to continue
The MCLECOMB has a date string 04/08/04 showing.
Guess they're not worried about Y2K. That could
be something specific for the EPIA chipset.
Now, you don't need a hex editor. You could use
Sysinternals "strings.exe" program. That is what
I used, to convert the eight files, into a big
glob of text.
http://technet.microsoft.com/en-us/bb897439
strings I0100116.BIN >> alltext.txt
strings AWARDEXT.ROM >> alltext.txt
strings ACPITBL.BIN >> alltext.txt
strings AWARDBMP.BMP >> alltext.txt
strings _EN_CODE.BIN >> alltext.txt
strings AWARDEYT.ROM >> alltext.txt
strings VPSD.BMP >> alltext.txt
strings MCLECOMB.ROM >> alltext.txt
Out of that mess, I get this. The first interesting
line seems to contain the BIOS string:
c. Awar$05/19/2004-VT8623-8235-CLE26I01C-00
are Inc.
tware ICLE26I01
Also, I see this in my alltext.txt file
Model: EPIA-M BIOS revision: 1.16
You might just see that BIOS string, displayed
on the first screen of the BIOS POST. Maybe
you'll see something like this, if your BIOS
was flashed to 1.16.
05/19/2004-VT8623-8235-CLE26I01C-00 <--- the "BIOS string"
Sometimes, when a BIOS maintainer updates their
BIOS, they forget to update the string. If
that date doesn't match the purported BIOS
release date, then that could be what has happened.
I think that's enough trivia for now
Have fun,
Paul
S
Searcher7
Yes, I did everything I was supposed to do to get to the screen that said, "BIOS Updated! Please power off or reset system".
That said, there is no question about it. The imbeciles must predominate over at VIA.
It would take common sense to create a motherboard that supports the minimum ability of playing video files. DVD or other. (And I'm not talking about doing high end stuff that a dedicated video editing machine does).
They couldn't learn english well enough to write manual instructions that made sense or get someone do who could do it. What happens on screen is definitely not exactly what is shown in the manual. And now they have a BIOS version posted for download that is the same as what ships on their motherboard. It is the same that is on the enclosed CD. And it is the same that is posted on their site, even though it is falsely labled a later version. (I'mnot sure there was even more than one version).
These are the only instructions I needed:
Type "vf-102.exe", press "Enter".
Type "1", press "enter".
Type "back1.bin", press "Enter".
Type "2", press "Enter".
Type "I0100116.bin, press "Enter".
I went through the above three times. The second time I got the message that "I0100116.bin" wasn't recognized, but the third time took like the first.
Two out of four USB ports never worked. Only the front and not the rear audio ports work.(Somewhat). I haven't tried the TV out, but even the printer I have that has worked with every machine over the years is flaky at best when attached to this pc.
I *again* downloaded the BIOS update that had the date, 10/14/2004, but after updating twice Belarc still gives me the 5/19/2004 date for my installedBIOS. (I doubt two versions were relaeased on the same day).
Perhaps it's not the BIOS and the chips are going bad going by the intermittant and progressive changes in the video/audio issues. Perhaps the BIOS isnot really being updated despite what it says. Either way the quality of this hardware is terrible.
Not one video file on my hard drive or DVD will work without either the video not working, the audio not working, or both not working. And that's if opening up a media player doesn't crash my system.
So since these problems cannot be solved any other way, it obviously means this motherboard was a big waste of time and money.
Perhaps I can find a different brand ITX motherboard that will fit into my ITX case.
Thanks.
Darren Harris
Staten Island, New York.
S
Searcher7
(e-mail address removed)2.com wrote: > On Friday, March 22, 2013 5:07:29 PM UTC-4, Patrick wrote: >> (e-mail address removed)2.com wrote: >> >>> On Thursday, March 21, 2013 7:36:22 PM UTC-4, Patrick wrote: >>>>> Ok. I'm going to try and follow your instructions because they seem >>>>> simple enough. >>>>> Butstarting on page 6 of that PDF mmanual it gets a little >>>>> confusing. (They really should have someone from the U.S.A. go over >>>>> all their printed instructions). >>>>> So let's see if I got this right. >>>>> 1) After I insert a formatted floppy disk, I double click >>>>> "drdflash", >>>>> which is on my desktop in order to create a bootable floppy disk. >>>> Yes! >>>>> 2) I then double click "vf-102", which is is on my USB flash drive, >>>>> and copy whatever it produces to the floppy. >>>> (Confusion) you should have a 'zip' file (that you downloaded) >>>> called 'VIA >>>> FlashTool 1..02' >>>> Double click this file and you should see this; >>>> https://www.dropbox.com/s/r8ovh6usj38ji6x/p1.jpg?m >>>> Double click the folder thus shown and you should see this; >>>> https://www.dropbox.com/s/2xr7e1kxghv9tbe/p2.jpg?m >>>> Now copy (only) the file 'vf-102' to the floppy. >>>> Ignoreor copy to your Desktop, the PDF file >>>> 'VIA_Flash_tool_User_Guide >>>>> 3) I also copy "I0100116" from my USB flash drive to the floppy. >>>> Correct, the file is actually called "I0100116.bin" which you will >>>> see by>>>> the 'DIR'command when you you boot from the floppy. >>>>> 4) When I reboot from the floppy, I type "vf-102.exe", and press >>>>> "Enter". >>>> Yes >>>>> 5) This will start me at the screen shown on page 6, where I type >>>>> "1" >>>>> and press "Enter". >>>> I'm not sure you need to press "Enter", I suspect the Input line >>>> will occur >>>> when you press the '1' >>>>> 6) Then I type in "bak1.bin" and press "Enter". >>>> Yes, Your old (previous) BIOS will now be saved to the floppy in >>>> case you >>>> want to put it back. >>>>> 7) Then I type "2" and press "Enter". >>>> I'm not sure you need to press "Enter", I suspect the Input line >>>> will occur >>>> when you press the '2' >>>>> 8) Then I type "I0100116" and press "Enter" >>>>Correction; Type "I0100116.bin" and press "Enter" >>>> Wait until it says that it's finished. >>>>> 9) Then I type "0" and press "Enter". >>>> I'm not sure you need to press "Enter", I suspect the Input line >>>> will occur >>>> when you press the '0' >>>>> Then it loses me when it says, "Execute vf-102, with the following >>>>> command line parameters."
This is getting too much for me. (I'll have to read that over several more times).
I can't see why backing up a BIOS twice using the exact same steps would result in any differences between the files unless there was some corruption involved. (That at least would make sense).
Darren Harris
Staten Island, New York.
P
Paul
The making of BAK1.bin is for emergencies. It is for, if you
get half way through flashing 1.16 and you're having problems.
You must not shut down, until you know a good BIOS flash has happened.
You could flash BAK1.bin back into the BIOS chip, if the 1.16 version
of file was not working.
The making of BAK2.bin, is for comparison to BAK1.bin. If both
files were the same, then you know the BIOS flash operation
did not happen. If BAK1.bin and BAK2.bin are different, then
something got updated.
I gave instructions as well, as to how to analyse a BIOS and
extract any text inside it. The text will include attempts
to place a date inside the BIOS. That's if you wanted to
do a more detailed analysis of any of the BIOS files you have
on hand.
Award 6.00 is not the BIOS revision. You look for information
presented on the first BIOS screen (POST), for information
about the version. In odd cases, the BIOS developer forgets to
change the version strings. There should be a "BIOS string"
on the screen, which contains unique identification.
Paul
M
Mike Easter
Why are you stating it like that? In those particular words instead of
a more straight-forward report that the tool reported BIOS updated?
Why are you saying 'I did everything blah blah' instead of saying:
"Yes, after I typed 2 and Enter and I0100116.bin and the tool went into
action I saw the flash tool report - BIOS Updated! Please power off or
reset system -"
At no time have you stated nor shown a graphic which convinces me that
you have seen the flash tool give you that BIOS updated report.
But why don't you say here the tool reported:
BIOS Updated!
Please power off or reset system
The first which what? Which you have never stated said
BIOS Updated!
Please power off or reset system
S
Searcher7
*** ?!? Because that is *exactly* what I saw on the screen. It's the same quote shown on page 7 of the manual.
Why are you saying 'I did everything blah blah' instead of saying: "Yes, after I typed 2 and Enter and I0100116.bin and the tool went into action I saw the flash tool report - BIOS Updated! Please power off or reset system -"
*** ?!? I listed the steps I took when I reached the part that said, "BIOS Updated! Please power off or reset system". I said I went through those steps three times, and the second time I got the message that "I0100116.bin" wasn't recognized, but the third time took like the first. (Provided you want to believe, "BIOS Updated! Please power off or reset system").
At no time have you stated nor shown a graphic which convinces me that you have seen the flash tool give you that BIOS updated report.
*** ?!? So you are saying that me saying that I saw the "BIOS updated report" is not proof enough. You have to see a picture?
*** ?!? I'll try again. I took all the steps necessary to update the BIOS. (Which weren't *exactly* the steps indicated in the manual). Two out of three times I did this I got to the message, "BIOS Updated! Please power off or reset system".
Now whether the BIOS was really updated or not I don't know, but that is what it said on the screen. And that is why I made the following statement: "....after updating twice Belarc still gives me the 5/19/2004 date for my installed BIOS."
Darren Harris
Staten Island, New York.
P
Patrick
Something that I checked, I booted to the Floppy and did this (at the 'A:/'
prompt);
"vf-102.exe /?" (press 'Enter')
Which gives the help dialog for 'vf-102.exe'
Below is the transcript of the result;
usage: A:\VF-102.EXE [-s backup.bin] [-p newbios.bin] [-r] [-c] [-b]
-s | --read: read flash and save into file
-p | --write: write file into flash
-r | --reboot: reboot after programming
-c | --clear cmos: clear cmos after programming
-b | --update bootblock: update BootBlock when programming
Note: When update AMI BIOS, you should add parameter '-b -c' !
Which is muchly the same as the Stuff shown in the PDF but illustrates the
'Usage' (Syntax).
I believe that the actual 'Usage: would be to remove the square brackets,
said brackets being to illustrate the usage of the 'switches' (-s,-p,-r,-c,
and -b) with thiere parameters (if any).
Thus (for instance) to do a Backup ('1') you would do;
A:\VF-102.EXE -s backup.bin
(and press 'Enter')
S
Searcher7
Via evidently thought it unnecessary to include such information, just like there is not a label on the BIOS chip, there is not reference to the version in BIOS.
I'll study what you wrote about analyzing the BIOS to see if I can do that.
But the bottom line is that either way, the issues with this motherboard will not be corrected, since it will either still have the same BIOS version because it A) doesn't really update or B) there is no later BIOS version than what I already had.
Or
The motherboard did get updated with a newer BIOS version that still has not corrected the problems.
Thanks.
Darren Harris
Staten Island, New York.
P
Paul
If I had your mini-ITX, I'd have to weigh...
1) Does the CPU have enough horsepower to *ever* be the multimedia
machine you hope for ?
2) The built-in GPU is marginal in terms of feature set. You know
that already.
3) You might try a PCI video card, which has support for decoding
acceleration for video. I see some HD5450 cards for PCI for example.
(Assuming you have an open PCI slot. HD5450 doesn't draw much power.)
But before spending the money, you'd need to do a bit of research
to see how much CPU is needed. The latest video decoders on
Nvidia and ATI video cards are pretty good (almost complete decoder),
so for *popular* movie formats, they should do most all of the work.
For some other non-Hollywood standards, I wouldn't be able to offer
any guarantees (DIVX?).
http://en.wikipedia.org/wiki/UVD
Cedar Radeоn HD 5400 Series UVD 2.2
(The HD5450 kinda gets kicked to the curb here... Pick something better,
if you can afford the power dissipation.)
http://www.anandtech.com/show/2931/4
If you had a PCI Express slot, you'd have more choices for video cards.
As far as the form factor goes, I think there were some mini-ITX sized
designs, with non-VIA hardware on them (from Zotac), which might make
a pretty decent base for an HTPC. Some of those had Intel processors,
and could likely decode completely in software (i.e. more horsepower).
HTH,
Paul
S
Searcher7
The Mini-ITX only has a single PCI slot, but I definitely won't be buying anything else for this machine. (Cheap low profile pci cards are difficult to come by anyway).
I don't knwow what you mean by multimedia machine, but I only want to be able to do the basics that any pc should be able to do. (Play DVDs and a variety of video file formats from my hard drive. (Stuff I could do with a 450Mhz machine 15 years ago).
I'll be attempting to figure out the BIOS version as per your instructions.
Someone also gave me this link: http://www.computerhope.com/issues/ch000234..htm
Thanks.
Darren Harris
Staten Island, New York.