Oerg866 wrote on 2026-05-02, 16:52:

K6INIT v1.5 is now released: - AMD K5 support (Write allocate & L1 Cache Control only) […]
Show full quote

The attachment fgdfgdfgdfgdfgdfg.png is no longer available

K6INIT v1.5 is now released:
- AMD K5 support (Write allocate & L1 Cache Control only)

https://github.com/oerg866/k6init/releases/tag/v1.5

Nice to have older amd cpu support (k5init+k6init=k56init). Whats with the picture attachement name?

marxveix wrote on 2026-05-03, 14:31:

Whats with the picture attachement name?

He did the mash (He did the keyboard mash)

NeoG_ wrote on 2026-05-03, 14:37:

marxveix wrote on 2026-05-03, 14:31:

Whats with the picture attachement name?

He did the mash (He did the keyboard mash)

He just typed what was under one hand fingers at his keyboard, its random name.

Oerg866
Thanks for the driver. I use it often in my retro PCs.
Yesterday I tried using the latest K6init driver to enable WA on a K5 PR166 processor, but it caused problems. Also, according to the WAMO utility, WA technology still didn't work. See the pictures.

Motherboard: GA-586SG (Sis5591) BIOS ver. 1.15.
Video card: Nvidia Riva TNT 16MB PCI, Detonator 2.08 driver.
I also tried it with an ATI Rage 128Gl 16MB AGP video card, but after booting, I only see a black screen. The driver version is Rage128-4.12.6282-win9x_6338cd20.
Everything works fine without use K6init.
This motherboard can automatically enable WA for the K5 processor, but only if the multiplier is set to x1.75.
I really want K6init to work correctly with K5 processors!

If you need help testing the driver, I'm happy to help. Thank you!

Please use K6INIT_D exe to produce some debug output to se if the correct bits are being written...

Thanks!

Oerg866 wrote on 2026-05-14, 17:29:

Please use K6INIT_D exe to produce some debug output to se if the correct bits are being written...

Thanks!

Yes please, I did.

I also tried enabling WA by replacing the graphics card with a S3 TRIO64/V2 2MB. The color inversion issue is gone, but WA mode still wouldn't activate.

Geoman wrote on 2025-01-13, 10:12:

IBM Aptiva 2168 / AMD K6 III+ ATZ / IBM PC DOS 7.0 gives me, while using DEVICE=K6INIT.EXE /auto in config.sys […]
Show full quote

IBM Aptiva 2168 / AMD K6 III+ ATZ / IBM PC DOS 7.0 gives me, while using DEVICE=K6INIT.EXE /auto in config.sys

Copy code to clipboard

1Keep C fatal error: Unable to fixup segment references

after that, the computer locks up.

Heyo. I've finally found the time to debug this. It's a bug in Geoff Chappell's (R.I.P. 🙁 ) CRTDRVR library.

A fixed version will come very shortly.

Hello all,

v1.6 is now released. Functionally, there are no changes, just a few niche fixes.

Changelog:
- The program cann now be loaded from CONFIG.SYS from IBM PC-DOS 7.xx (and I suspect a few other DOS variants are now fixed as well) without crashing.
- The program no longer corrupts the screen on redirection using ">", the content of the redirection target is now also correct.

Since all of the console handling code was rewritten from scratch, there may still be bugs in this area -> Please report 😀

https://github.com/oerg866/k6init/releases/tag/v1.6

Best
Eric

Hello,
Sorry if it not a proper question for this thread.
I am impressed by your work and was wondering if there is a similar version of this program for Win98, updated to that extent I mean.
I know there are several like CTU but I always find those programs buggy.

Thanks

Mamba wrote on 2026-09-17, 11:04:

I know there are several like CTU but I always find those programs buggy.

What is happening with CTU? It works fine on my K6-2+ system. Avoid loading any other K6 booster before windows loads and set your profile to load on windows startup.

NeoG_ wrote on 2026-09-17, 11:52:

Mamba wrote on 2026-09-17, 11:04:

I know there are several like CTU but I always find those programs buggy.

What is happening with CTU? It works fine on my K6-2+ system. Avoid loading any other K6 booster before windows loads and set your profile to load on windows startup.

I am not able to understand how to work with mtrr(s) memory addresses. Not sure which intervals I need to pick.

Would it be possible to use this program in conjunction with Windows98, meaning it loads before the OS?

Mamba wrote on 2026-09-17, 13:30:

I am not able to understand how to work with mtrr(s) memory addresses. Not sure which intervals I need to pick.

K6INIT in DOS will tell you what the MTRR start address is, then select the amount of memory on the GPU and set the memory range to write combined. In my case K6INIT says the MTRR address is C8000000, I use this value for MTRR0 and I set the memory size to 16MB to match the Voodoo 3's memory size.

NeoG_ wrote on 2026-09-18, 08:31:

Mamba wrote on 2026-09-17, 13:30:

I am not able to understand how to work with mtrr(s) memory addresses. Not sure which intervals I need to pick.

K6INIT in DOS will tell you what the MTRR start address is, then select the amount of memory on the GPU and set the memory range to write combined. In my case K6INIT says the MTRR address is C8000000, I use this value for MTRR0 and I set the memory size to 16MB to match the Voodoo 3's memory size.

Thank you!
What if there are two mtrr?
I mean if I start ctu I see mtrr0 with 128kb and mtrr1 with “x” megabyte.
GeForce GTS 32mb

Mamba wrote on 2026-09-18, 09:02:

Thank you! What if there are two mtrr? I mean if I start ctu I see mtrr0 with 128kb and mtrr1 with “x” megabyte. GeForce GTS 32m […]
Show full quote

Thank you!
What if there are two mtrr?
I mean if I start ctu I see mtrr0 with 128kb and mtrr1 with “x” megabyte.
GeForce GTS 32mb

The smaller one is the VGA memory area, the larger one is the LFB memory area. If you want both VGA and LFB write combining in windows 98 you can set both. In case you only want LFB just use the larger one with 32mb as the size in CTU.

In my case, since my K6-2+/550 is fast enough for any VGA game without MTRR/WC, I don't use write combining in the VGA area to maximise compatibility. It doesn't provide any substantial difference in user experience except benchmarks. For example in OMF2097 it causes some screen corruption with animations on my voodoo3.

Is there a way to see both vga memory area and lfb memory area addresses?
Just to be sure I won’t mess with areas using mtrr0 to put 128kb and mtrr1 to put 32mb

Mamba wrote on 2026-09-18, 10:51:

Is there a way to see both vga memory area and lfb memory area addresses?
Just to be sure I won’t mess with areas using mtrr0 to put 128kb and mtrr1 to put 32mb

The legacy VGA memory area is always at address 0xA0000. The linear frame buffer address can be listed by any VESA utilities. One such program is attached. You should look at 'LFB is located at: xxx'.

Falcosoft wrote on 2026-09-18, 11:19:

Mamba wrote on 2026-09-18, 10:51:

Is there a way to see both vga memory area and lfb memory area addresses?
Just to be sure I won’t mess with areas using mtrr0 to put 128kb and mtrr1 to put 32mb

The legacy VGA memory area is always at address 0xA0000. The linear frame buffer address can be listed by any VESA utilities. One such program is attached. You should look at 'LFB is located at: xxx'.

The attachment VESAINFO.zip is no longer available

Thanks

Regarding the question earlier.

It is planned in the distant future to write a Windows 9x driver that does the same thing as K6INIT.