Is Direct X 8.0 different from 8.0a?

When I download 8.0a from www.microsoft.com, the downloaded file says I've got 8.0. Are 8.0 and 8.0a the same? Thanks. James

Yep, I noticed the same thing. MS didn't rename the download to make it obvious it was a new version, so I thought I'd got 8.0 again. However, the controller problems I had with 8.0 were fixed with the new file, so it must be defferent. "James Larson" <[email hidden]> wrote in message news:[email hidden]... > When I download 8.0a from www.microsoft.com, the downloaded file says I'vegot > 8.0. Are 8.0 and 8.0a the same? Thanks. > > James

James.... Here's a few "hints" on installing DirectX on your computer. Understand.....this stuff comes from the "experience" of people who work with DirectX API's as their job.....and some of my own experience over the last two years (building computers and installing high-end components): 1. The DX file you download from MS website(s).....are named for the "DX Installer" program....not for the version of DX it contains. That is why the DX8.0a download software/program...has a file name of DX8.0. This is the installer...not the actual version of DX it contains. Hope that is clear? 2. As a good rule to follow, you should reinstall DirectX anytime you add a new piece of hardware, a significant piece of software (ops or a "game") or make significant changes in any "settings" on your computer. Also, after every BIOS update/change....or chipset update or change. In fact...when in doubt....reinstall DirectX. That's a good rule to follow...and will not ever hurt you. I keep a copy of the DirectX installer permanently in my Windows/Temp folder......and that is where you should always install it from....no where else (Start/Run/Windows/Temp). 3. When ever your system starts acting up......always consider a corrupted DirectX component file as a "possible" solution. I reinstall DirectX first....before trying anything else......when my system starts having problems. Two in ten times.....that's the problem. Those are not bad odds. 4. Put a copy of DXDiag on your desktop as an icon. Run DXDiag as part of any troubleshooting routine....it often can help you identify a problem source. (The executable for DXDiag can be found in: c:\Programs\DirectX\Setup. Right-click the file, choose "send to desktop"...and bingo...you have the icon on your desktop for quick and easy access). If you have a serious problem....run DXDiag...and choose "Save All Information" ...its a "button-bar" on the lower right side of the DXDiag box. This will put a copy of "DxDiag.txt" in your Windows, "My Documents" folder by default. You can open this with "Notepad" and then "print it" right away. Save a copy of this in a notebook for your computer...or someplace you can access it easily. This "report" is for the "session" you just open in DXDiag (later sessions...if you choose "Save All Information"....will overwrite the DxDiag.txt file...which is fine if you have printed the previous session report). It contains much more detailed information about your system, operating files and DX files than does the onscreen version of the DXDiag session. Make sure you regularly run DXDiag (I run it weekly) to check for corrupted files...or "registry" problems with key components such as video card drivers, control device drivers, sound card drivers, etc. 5. THIS IS VERY IMPORTANT! Even though MS, and conventional wisdom says, if you re-install DirectX it will overwrite existing DX files (newer date versions always overwrite older date versions...but not the reverse). However, "experience" says this is not true....in all cases. In fact, the MS KB site is full of documents that have MS actually admitting cases where a corrupted DX file...will not be overwritten by a reinstall of DX. So....you can't count on this fact.....no way. If I suspect a particular DX file to be corrupted....what I do is "rename" the file by putting an "x" in front of the name......or you can rename it by changing the extension to ".bak"....this will always be allowed. Then, after re-installing DX...I go to the folder where the suspected corrupted file is....and check to make sure I have a new, fresh copy there. I can not tell you how many times in the last year I've done this (after re-installing DX several times with no problem resolution)......and bingo....the problem suddenly is gone! If you know for sure you have a corrupted DX file...but are not sure which one (after a while, you will learn what files are for what purposes)......then take the time to go to your printed DxDiag.txt copy.......take the first page that lists every DX file on your computer.....and using "Start/Find/Files and Folders"......enter each one, and then right click and delete it.....or to be safe, right-click and use the "rename with an x" technique above. This might take you an hour....but how long have you spent hunting down a problem already. An hour is a savings of time...usually! This will insure that a corrupted DX file(s)....gets replaced with a fresh, uncorrupted one. Hope this is clear? Okay, James....that's everything I know about DX....how to make it work for you on your system! Hope this helps you out. Regards, Tom Pabst

Tom, I think you're probably the only one in the world who re-installs DirectX after installing a new game/app. That's all good advice for people who are actually having problems, and have run out of other things to try, but otherwise it's unnecessary. I'm guessing you must have had some *really* bad experiences with it. "Tom Pabst" <[email hidden]> wrote in message news:r2M07.153514$%[email hidden]... > James.... ><snip> > > Regards, > > Tom Pabst

James, There's now a DX8.1 *beta* floating around the Net...apparently withOUT Microsoft's blessing. I'm afraid to try it, but by all reports, it's pretty good. --Steve Smith "James Larson" <[email hidden]> wrote in message news:[email hidden]... > When I download 8.0a from www.microsoft.com, the downloaded file says I'vegot > 8.0. Are 8.0 and 8.0a the same? Thanks. > > James

"Stephen Smith" <[email hidden]> wrote in message news:I%317.86807$[email hidden]... > James, > > There's now a DX8.1 *beta* floating around the Net...apparently withOUT > Microsoft's blessing. I'm afraid to try it, but by all reports, it'spretty > good. > > --Steve Smith > It *is* pretty good, uh, not that I'd know first hand, of course. :-) Jerry Morelock

On Thu, 05 Jul 2001 20:22:00 GMT, "Stephen Smith" <[email hidden]> wrote: >James, > >There's now a DX8.1 *beta* floating around the Net...apparently withOUT >Microsoft's blessing. I'm afraid to try it, but by all reports, it's pretty >good. > I've been using it for quite some time and have had no problems with it. But, I had no problems with 8.0a either so there was no real reason for me to install it either.

Simon.... I learned to do this.....from pretty common "tips" of the same instructions on most of the techy boards. And, you'll find this often in the MSKB....usually buried because MS doesn't like to admit to it too loudly. DirectX interfaces with nearly every function on your computer.....not just games or video or sound. Before I started this "habit"......computer problems were more frequent....maybe its a coincidence. But, you'd be in the minority thinking you can just install DX and forget about it. Tom

On Sat, 07 Jul 2001 09:23:14 GMT, "Tom Pabst" <[email hidden]> wrote:

Quoted text (13 lines)

>Simon.... > >I learned to do this.....from pretty common "tips" of the same instructions >on most of the techy boards. And, you'll find this often in the >MSKB....usually buried because MS doesn't like to admit to it too loudly. >DirectX interfaces with nearly every function on your computer.....not just >games or video or sound. Before I started this "habit"......computer >problems were more frequent....maybe its a coincidence. But, you'd be in >the minority thinking you can just install DX and forget about it. > >Tom > >

I don't think he's in the minority. You are the first person I've seen make mention of corrupted directx files. I've certainly had no problems with corrupted directx files since it's first release onto the market.

In article <6yA17.159226$%[email hidden]>, "Tom Pabst" <[email hidden]> writes:

Quoted text (10 lines)

>Simon.... > >I learned to do this.....from pretty common "tips" of the same instructions >on most of the techy boards. And, you'll find this often in the >MSKB....usually buried because MS doesn't like to admit to it too loudly. >DirectX interfaces with nearly every function on your computer.....not just >games or video or sound. Before I started this "habit"......computer >problems were more frequent....maybe its a coincidence. But, you'd be in >the minority thinking you can just install DX and forget about it. >

I've never had to re-install DX either, but then again I'm still running DX7a. What does it(DX corruption) cause? I wasn't paying attention earlier... Eldred -- Dale Earnhardt, Sr. R.I.P. 1951-2001 Homepage - http://www.umich.edu/~epickett F1 hcp. +16.36...Monster +366.59... Never argue with an idiot. He brings you down to his level, then beats you with experience... Remove SPAM-OFF to reply.

Tom, My news account doesn't show your reply, so I didn't know you'd replied until Noddy posted. All I can say is that we've got three PC's in my house, and over the years since DirectX 3 we've installed countless games/applications/operating systems/add-on cards/new motherboard/cpu's etc etc, and haven't yet found a need to re-install DirectX. Obviously the DirectX dlls are some of the most used files on any PC, so if you get a disk problem or a bad crash, there's always a chance they could be affected, same with any of your windows system files. Then again, I'm still using a BX board, which makes games/hardware/drivers/upgrades/problem solving all a lot simpler. I program using DirectX myself, and have done since DX5. In particular with D3D, DInput and DDraw. Despite all the inevitable crashes when I get something wrong, i've yet to have any corrupt DX files. "Noddy" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (7 lines)

> On Sat, 07 Jul 2001 09:23:14 GMT, "Tom Pabst" <[email hidden]> > wrote: > > I don't think he's in the minority. You are the first person I've seen > make mention of corrupted directx files. I've certainly had no > problems with corrupted directx files since it's first release onto > the market.

On Sun, 08 Jul 2001 01:10:19 GMT, "Simon Brown" <[email hidden]> wrote:

Quoted text (21 lines)

>Tom, > >My news account doesn't show your reply, so I didn't know you'd replied >until Noddy posted. > >All I can say is that we've got three PC's in my house, and over the years >since DirectX 3 we've installed countless games/applications/operating >systems/add-on cards/new motherboard/cpu's etc etc, and haven't yet found a >need to re-install DirectX. > >Obviously the DirectX dlls are some of the most used files on any PC, so if >you get a disk problem or a bad crash, there's always a chance they could be >affected, same with any of your windows system files. > >Then again, I'm still using a BX board, which makes >games/hardware/drivers/upgrades/problem solving all a lot simpler. > >I program using DirectX myself, and have done since DX5. In particular with >D3D, DInput and DDraw. Despite all the inevitable crashes when I get >something wrong, i've yet to have any corrupt DX files. >

He also said that if you do get corrupted dx files and reinstall directx it won't overwrite the corrupted files. Is that true?

> He also said that if you do get corrupted dx files and reinstall > directx it won't overwrite the corrupted files. Is that true? Dunno to be honest, I suppose it could be. Haven't had that problem.

Tom, I just wanted to thank you for taking the time to post such a detailed and informative reply to my question about DX8.0 and DX8.0a. It was extremely helpful to everyone who read it, I'm sure. Thanks again! James Larson