Grumalg

Was just trying to help a bit... I've done some pretty extensive MSWord docs and converted them to PDF and HTML. You can find an example ~80 page set of tables extensively internally hyperlinked with a massive amount of embedded images in tables here: https://forums.civfanatics.com/resources/civ-vi-reference.25734/ It started as MSWord tables and wound up as both PDF and HTML for website use. If you need help or more suggestions, I'll happily provide them.

A couple of notes: Both Open Office and Libre Office can import .doc *and* export it as PDF - both are freeware. MSWord itself can Save As .html which would convert your table to html. There are some caveats if the .doc has images, but they wouldn't apply to just your table.

I'm aware DirectX is supposed to carry all back versions and aware for some older games you need to pass the actual 9.0c across it before it will work. I didn't know whether SimCity 4 was one of the ones that needed the original 9.0c or not, thus suggested passing it across again in case as doing so is harmless. Besides, it's possible someone could be fighting a damaged DirectX install. Reinstalling it is an easier fix to describe online than trying to walk people through dxdiag...

I run an I5 4670 w/ 16 Gb Ram and an Nvidia 760 (1152 cuda cores w/3Gb vram) driving dual 27" 2560x1440 monitors running Win 7 Pro 64. I've been able to run windowed or fullscreen in 2560x1440, but only in software rendering mode. Since the game engine can't handle hi-res textures in software mode, I chased being able to run in hardware rendering mode at the highest resolution I could get (which turned out to be 1920x1200). Getting hardware rendering working right can be fairly complex. The following are the things I went though getting there... 'Hardware' rendering is DirectX. The game was written to DIrectX 9.0c. If you're not *sure* you have that, you can DL and install it from here: https://www.microsoft.com/en-us/download/details.aspx?id=35 It won't hurt anything to reinstall it if you already have it but didn't know. Then you want to edit Graphic Rules.sgr and Video Cards.sgr in the program files (x86) directory (not being more specific because different game sellers use different install directory names). You can find a guide to that here: When the game was written the video hardware we use today didn't exist. At startup the game looks in the .sgr files to determine what the video is capable of and configures for that. If your video hardware isn't listed in the .sgr's it will default to the safest setting (which is also the lowest quality and slowest). If you can't find the proper values for your video per the above, you can always use GPU-Z to obtain those values: https://www.techpowerup.com/gpuz/ There's also a video here: Which can be useful even if your not running Win 10. In the 'More' below the video are links to files with the further changes you need to make in .sgr files(which aren't the same as the forum based guide above - and are specifically aimed at smoother scrolling in the game) Finally, while you can edit the command line parameters in the shortcut to the game to try different things to see what will work for you, it's easier to use one of the game launchers which will give you settings on tabs to specify how the game will be launched. This speeds up making multiple tests with different settings. After trying several I settled on this one: I've read the hardware rendering in the game engine can't handle values 2000 or larger in the resolution. Best I could get was 1920x1200. Running the game even at that resolution results in hard to read UI text. There's a mod to fix that you can find here: Hope some of that proves useful...

I'm still running Win 7, so I don't have 8 or 10 to test with. I.E. no I haven't tested it. If you do some searching like "XP Mode Win 8" or "XP Mode Win 10" you get a ton of hits with people telling how it's dine.

The 'N' version is just XP Mode without Media Player...

I think there's a bit of confusion in the above 'XP Mode' discussion. The picture CorinaMarie posted is not 'XP Mode', but 'Compatibility Mode'. Compatibility Mode tries to make the OS *look* like XP to an application (and often succeeds). XP Mode means running a virtual machine on your PC that's actually running XP and running an application *in* that running version of XP. XP mode exists because Microsoft dropped supporting 16 bit applications as of Windows 7 (which only supports 32/64 bit applications). However many businesses were *still* depending on 16 bit apps. To avoid losing Win 7 sales and to avoid the cost of still supporting XP, XP Mode was born. It consists of two things: 1) Windows Virtual PC https://www.microsoft.com/en-us/download/details.aspx?id=3702 2) Windows XP Mode https://www.microsoft.com/en-us/download/details.aspx%3Fid=8002 You first install MS virtual PC and then install XP Mode *in* a virtual PC so you have an actual XP running on your system. XP Mode does some magic to make the application's GUI running in Virtual PC/XP Mode appear on the normal Win 7 desktop appearing to the user as a normal win 7 app. There's no compatibility involved here, the app is actually running in XP, just getting keyboard/mouse passed to it from Win 7 and taking it's output out to the Win 7 display. I use it to play old 16 bit apps on my win 7 system, but 32 bit apps work just as well... When you start an app in XP Mode, the virtual machine silently, invisibly starts and you interact with the app as if it was installed in Win 7, without working in a virtual machine window. Microsoft says it's Virtual PC and XP Mode are only for Win 7, but a bit of searching will show you people are using it in Win 8 and Win 10. They are putting up 'how to's all over the internet on the subject. One limiting factor though, MS Virtual PC only runs on Win 7 Pro or higher, home versions need not apply...