Links 2003 not working with Windows 10

[Mailman]

I have tried with and without a modified Videocard.txt file but Links is picking up and identifying my 4060Ti GPU either way. I know you stated that you had changed your Videocard.txt file but did you change any of the videocard configuration parameters for your particular GPU ?

To my knowledge I had not changed any of the videocard configuration parameters when I first got 2003 to run (I have since monkeyed with anti-aliasing and a few other settings but changed them back since I didn't see any appreciable difference in the display quality). And I say "to my knowledge" because I was trying all kinds of things at the height of my effort to get 2003 to run. I can confirm that I did change the Videocard.txt file (but my sense is that that didn't have an effect one way or another) and my registry display mode is set at 14; I believe that is all I did after I unwound all my prior efforts and started over with a clean 2003 reinstall. But again, I could be wrong - those two days when I was doing all this stuff is kind of blur at this point.

That said, happy to check any of my settings etc. Just let me know what you'd like me to check.

Took a while again to restart Links via LinksLauncher but it did after what seemed like an eternity (5-10 mins)

Again took a while to restart Links via LinksLaucher but again it did

Not instanteous but at least it did start via LinksMMIII

When you talk about "took a while", "not instantaneous", etc., here are you referring to the number of attempts or the amount of actual time (i.e., clock time) that it takes 2003 to finally start? I ask, because if the latter, that actually reminds me of what I was seeing about three years ago before my (former) hard drive crashed and burned (not literally of course). Programs would sometimes start fine, other times not . . . hardly happened at all at first, then got progressively more commonplace, until finally one day I couldn't even boot up . . . any chance your hard drive might be on its way out? Have you noticed what you're seeing with 2003 when you try to run other programs?

No sir. Only Links is doing this. Everything else running fine.

Re the videocard.txt could you check the line where you might have detailed your specific GPU and possibly put in some of the parameters listed at the very top of this file. The parameters I reproduce here. Probably makes no difference but you never know.

// SceneRenderer // Scene based renderer (eg: PowerVR, Kyro etc...)
// NoAlphaTest // Disable alpha test (conflicts with other modes)
// NoTriLinear // Do not attempt trilinear filtering
// NoTripleBuffer // Do not attempt triple buffering
// DefaultBltNotFlip // In full screen mode, use BLT
// NoFog // Do not attempt fog
// TextureOffset // Texel offset for fonts is done on x,y's not u,v (eg: Riva128)
// BrokenAlphaTest // Cards that cannot do Alpha test without ALPHABLEND being enabled (eg: ATI Rage)
// RenderEqualZ // Render bit depth must equal Z bit depth (eg: nVidia cards)
// NoParallelism // Lock the back buffer after rendering (eg: Voodoo3 - queueing up too many blits)
// BadMouse // Card can never use GDI mouse (eg: Voodoo)
// LowEndCard // This is a 'low end' card - the application can request this is not supported in hardware
// NoMipMap // Disable mipmaps
// Bad4444 // Disable 4444 textures (eg: Chromatic Mpact)
// BadAGP // Disable AGP textures (eg: Chromatic Mpact)
// NoDisablePerspective // Disable disabling perspective correct texturing (eg: Voodoo cards)
// LimitTextureSize // Limit texture size to 256*256 to correct bad caps
// ForceSquareTextures // Do not allow non-square textures
// NoStretchTexture // Force system memory stretch blit to square up textures
// AllowLowMemoryCard // Allow card to bypass low texture memory test (eg: Voodoo2)
// NoMultitexture // Disable multitexture blending modes
// Disable1024x768 // Disable video modes 1024*768 and above
// Disable1600x1200 // Disable video modes 1600*1200 and above
// DisableTextureDeletes // Try not to delete textures (eg: Intel 740)
// SlowDisplayModeChange // Prevent video drivers that take a while before sending the WM_DISPLAYCHANGE msg from getting stuck in an endless loop of display mode changes (eg: Savage 4)
// DisableColorControl // Disable gamma and color controls
// Limit500VidTextures // Limit video memory textures to 500 (eg: Riva 128)
// Bad8888 // Disable 32 bit textures (eg: Voodoo)
// BadVideoCard // warn user that this video card may not work with Links
// NoCopyZInVidMem // don't put the z-buffer copy into video memory

[Lobofan]

No sir. Only Links is doing this. Everything else running fine.

Ok, well, so much for that idea.

Re the videocard.txt could you check the line where you might have detailed your specific GPU and possibly put in some of the parameters listed at the very top of this file.

Here is what I added to the videocard.txt file:
0x67DF = "Radeon RX 570 Series"
DefaultBltNotFlip
NoCopyZInVidMem

I believe the parameters I added were per the guidance I found in whatever thread detailed how to do this . . . memory is starting to fade as to specifics with respect to origin. Does this help?

[Mailman]

Here is what I added to the videocard.txt file:
0x67DF = "Radeon RX 570 Series"
DefaultBltNotFlip
NoCopyZInVidMem

I believe the parameters I added were per the guidance I found in whatever thread detailed how to do this . . . memory is starting to fade as to specifics with respect to origin. Does this help?

As per https://www.linkscountryclub.com/help/n ... eocard-txt

I may have another look at this file.

[Lobofan]

Yes! It was the Links Country Club . . . like I said, it's all a bit of blur at this point.

Hope that the videocard.txt is the answer!

[Mailman]

Hope that the videocard.txt is the answer!

Made no difference

However a slightly more interesting experience the last couple of days has been to

• 1. Continue with having Links MMIII.exe on the taskbar and attempt running it from there (rather than a shortcut or using LinksLauncher)
  2. Have Links MMIII.exe set up in compatibility mode to 'Disable full-screen optimisations no other settings changed.
  3. Leave desktop resolution at its native 2560x1440 (native) setting.
  4. Leave scaling mode at the default 'aspect ratio' within the Nvidia Control Panel.
  5. Perform Scaling on Display (default setting) with the override button left unchecked.
  6. Mode 14 selected in the registry (1920x1080) as before.
  7. No changes to the videocard.txt file

This may be just one of these transitory things and I still am yet to be able to start Links 2003 on demand but now taking less than 10 re-starts although I probably jinxed it having added all my courses (or rather the links to where they reside).

[Lobofan]

Made no difference

That would have been too easy I suppose.

4. Leave scaling mode at the default 'aspect ratio' within the Nvidia Control Panel.
5. Perform Scaling on Display (default setting) with the override button left unchecked.

We have different video card manufacturers, but my scaling mode is essentially set the same as yours. My GPU scaling function can only be enabled or disabled, right now it's set on enabled which I interpret as being in "override" mode. What happens when you check the "override" button?

This may be just one of these transitory things and I still am yet to be able to start Links 2003 on demand but now taking less than 10 re-starts

Is "less than 10 restarts" the best you've gotten thus far? I ask, because that 2003 starts at all, albeit only intermittently, must mean you're getting close. Check box here, setting change there . . . got to be something.

[Mailman]

Is "less than 10 restarts" the best you've gotten thus far? I ask, because that 2003 starts at all, albeit only intermittently, must mean you're getting close. Check box here, setting change there . . . got to be something.

Just before retiring - took me about 15-20 I reckon so it has started every time today I've tried today - just need to keep restarting

At least I don't need to change the desktop resolution settings now.

Now 2 months but at least this is the closest I have got - it has installed and runs great when it starts

Yes perhaps that elusive checkbox somewhere

Def Links and my machine are wrestling over resolution it seems

I may try the very latest Nvidia driver on Sunday as well. There was a new motherboard BIOS released in mid-May as well so may try that as well after a bit of research on what it does.

[dwg]

Over the years different Nvidia driver versions have given vastly different results, I recall the day when you would identify a good version and stick to it.

On my Linux notebook I only found a Nvidia driver version this week that works relatively well with Links, prior to this the embedded Intel GPU was running rings around the Nvidia GPU, the version I am currently using is 570.133.07. I have tried around 5 family's of drivers. On my Linux desktop, I can only use a Legacy Nvidia driver and the performance there is rubbish, to the point I removed the HBA.

[SammieDog]

Is "less than 10 restarts" the best you've gotten thus far? I ask, because that 2003 starts at all, albeit only intermittently, must mean you're getting close. Check box here, setting change there . . . got to be something.

Just before retiring - took me about 15-20 I reckon so it has started every time today I've tried today - just need to keep restarting

At least I don't need to change the desktop resolution settings now.

Now 2 months but at least this is the closest I have got - it has installed and runs great when it starts

Yes perhaps that elusive checkbox somewhere

Def Links and my machine are wrestling over resolution it seems

I may try the very latest Nvidia driver on Sunday as well. There was a new motherboard BIOS released in mid-May as well so may try that as well after a bit of research on what it does.

Andy, I got new computer a few months back. AMD Ryzen 9 9900X, RTX 4070 GPU, 2TB NVMe drive split into 2 partitions (1 for OS and programs and I have Links installed on the 2nd partition). Had no real problems installing Links other than the highest registry setting that I can use for the screen display is 13. Best of luck. BTW still at RM !!

Robert

[Mailman]

Andy, I got new computer a few months back. AMD Ryzen 9 9900X, RTX 4070 GPU, 2TB NVMe drive split into 2 partitions (1 for OS and programs and I have Links installed on the 2nd partition). Had no real problems installing Links other than the highest registry setting that I can use for the screen display is 13. Best of luck. BTW still at RM !!

Robert

I actually got round to playing 9 holes today at Shinnecock HD which was fun apart from the putting Back and forth I went on Hole #2 on M(c)/M(c). Played at RTS (as I always have). The difference between hitting the ball 5 feet and 25 feet is like an angstrom of extra distance on the mouse. Still I managed a couple of birdies so that was something I've now been retired from RM for 7 years believe it or not - where has that time gone?

Back to my troubles, I updated my Asrock BIOS to the latest May version (v3.26 on a PG Riptide 850) - all stable from what I can tell. Now about to try the latest Nvidia May driver as well.

The same symptoms persist i.e the starting aspect but once it does Links behaves in-game (apart from the putting that is )