| |||||||
| General OS Tweaks Questions, info, results for various OS tweaks and OS tweaking apps. |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | |
| I can't really recall when I first noticed these problems, but among other issues, I couldn't access my printer settings and my settings wouldn't save on exiting. So after consulting the KB, I decided to do a re-install of the OS (W2K) and all appropriate patches and service packs. This corrected the other problems that I was having, but now I have an even bigger mess. Specifically, when I try to run a couple of programs (BF1942 for example) I get the following error: BF1942.exe couldn't find entry point DdEntry1 in GDI32.dll. And then, NOTHING, back to the desktop. Other programs are fine, and the KB doesn't provide much help on this. Anybody have an idea on how to fix this? | ||
| | | |
| | #8 (permalink) | |
| some games are sensitive to what areas of ram their resource files are stored on, if you have your system overclocked it might be affecting this area of ram (corruption) and making the game just not run...as a matter of fact, games are one of the best ways to test both your ram..and an experimental overclock, so if yer running into problems, and have exhausted all other possible explanations, then try bringing your clox down a bit...unless...of course...you arent overclocked at all, then you are FUBAR.... | ||
| | | |
| | #9 (permalink) | |
| another possibility is that the CRC (cyclic redundancy check) or checksum of that file or resource might be bad, this can be caused by....say it with me....overclocking, but more often than not, is caused by a dirty or scratched installation cd or a "bad" download, so if you can, pull those cds out, take a good look at them, tell them you love them, clean them, put them in your cd rom, install them, then have a smoke afterwards, and pray that im right... its like i always say... "anything to prove it aint the puter doin it" | ||
| | | |
| | #11 (permalink) | |
| The system is a tad overclocked. 166X10.5 vs 133X12.5. This entry point problem didn't happen until AFTER the OS reinstall, so I doubt that this is the cause. I will check, but I'm not holding my breath. This program is not downloaded, it is a pseudo-legit install (ie, my friend gave me the game to play in trade for one of mine) I can say for sure that this is not the only program that I am having the problem on, it is just the one that irks me the most The systemtray icon for the ATI control panel also causes the exact same problem. Other thoughts? | ||
| | | |
| | #16 (permalink) | |
| Thanks for the link AntiM. I should've known someone would have come up with it. Here's what I was relying on from MS: Q. How do I uninstall DirectX? A. DirectX 9.0 is a system component and cannot be uninstalled. If there is a problem with the DirectX installation, it can normally be resolved by shutting down all running applications and reinstalling. As mentioned previously, DirectX 9.0 is fully backward-compatible with titles written for previous versions of DirectX. If you are having other problems after installing DirectX 9.0, these can often be resolved by installing updated drivers for your display card, audio card, or input device. | ||
| | | |
| | #17 (permalink) | |
| DX7 and 8 games and apps don't run quite as well under 9. 3dmark2001 is down a few hundred points from DX8. And games seem to be more sensitive to overclocking. It's reasonably stable on XP pro. But from what I've gathered from various posts here and elsewhere, I think it's probably less stable on other OS's. | ||
| | | |
| | #18 (permalink) | |
| My thought is that yeah, it still ought to be in beta... it has to keep performance the same or better, across the board, before they can push it like they are now. But whatever, Microsoft doesn't give a **** about what anyone thinks, they only care about their bottom line. Last edited by TheOutcast; 10-June-03 at 12:55 PM.. | ||
| | | |
| | #19 (permalink) | |
| Good info about the uninstaller AntiM but the fact is that none of these DX9A to DX8 uninstallers completely uninstall DX9A, goto Run and type DXDIAG and look at the files and versions, also compate the filesizes to that of DX9A, most are the same as DX9A ![]() The only way truly back to DX8 is (1)system restore, (2)booting from XP CD and running "repair an existing windows installation", or (3)formatting ![]() | ||
| | | |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Slashdot // Do You Tell a Job Candidate How Badly They Did? | Gizmo | Slashdot RSS | 0 | 10-January-07 11:30 PM |
| I need help badly with this Physics question | AMD Daddy | Anything Goes | 19 | 03-March-05 08:37 PM |
| box stealing? help needed badly | Cibressus | Anything Goes | 22 | 11-November-04 07:37 PM |
| system FUBAR... request assistance | sno2dude | Other PC Problem / Help | 33 | 19-September-02 09:24 PM |