Apologies if this is a silly question but how do you get the log file out of Witchery when run with LOADLIN.EXE?

I'd also like to know this ^, I am running witchery from freedos usb stick. And thank you fagear for looking into my ramdac error. I did try to run with the -e3 option, got the same results except it dropped one line in the possible connections to check, the pin 63 = pin 43 line between fbi and ramdac isn't there using this option.

And an update on my sli board(when connected to this mainboard). Witchery did accurately describe the correct fb ram chip to check/replace and now my sli board passes all witchery tests.

zuldan wrote on 2026-07-20, 08:50:

Apologies if this is a silly question but how do you get the log file out of Witchery when run with LOADLIN.EXE?

You type "ds" to get NC/VC/MC-like lightweight file manager to copy logs to automounted drives.

Fagear wrote on 2026-07-22, 18:20:

You type "ds" to get NC/VC/MC-like lightweight file manager to copy logs to automounted drives. […]
Show full quote

zuldan wrote on 2026-07-20, 08:50:

Apologies if this is a silly question but how do you get the log file out of Witchery when run with LOADLIN.EXE?

You type "ds" to get NC/VC/MC-like lightweight file manager to copy logs to automounted drives.

The attachment 2026-07-22 21.18.38.png is no longer available

The attachment 2026-07-22 21.17.01.png is no longer available

So simple, thank you

Fagear wrote on 2026-07-17, 23:33:

May I ask here? What log filename is better in you opinion: 1) 260717_22-26-28_witchery.log 2) witchery_260717_22-26-28.log […]
Show full quote

May I ask here?
What log filename is better in you opinion:
1) 260717_22-26-28_witchery.log
2) witchery_260717_22-26-28.log

Definitely name preceding the date, otherwise things get lost between other files. Year should be 4 digits, it sorts "better" and avoids any confusions with what order different bits are.
I don't think seconds are necessary with time, the tests take forever and you won't get things happen within the same minute...

Ok, got it. Changed the name template of the log files.

Also rewritten RAMDAC detection procedure to improve detection accuracy.

Doing some work on TMU connection and pipeline rendering tests.
Some progress there: Witchery now can test connection for all three TMUs that are possible.
Very simple pipeline rendering test is implemented that also can use any of the TMUs and it can test TMU with and without its RAM. So now its possible to discern which TMU has problems and are those problems in FT/TF busses or in RAM connections.

Note that no detailed analysis is implemented now, only stating the approximate fault location.

Many more updates are ready under the hood:
- communication with optional CVBS/YC encoder (for TV-out) is implemented
- added proper support for Canopus Pure 3D II board
- FT/TF bus scan optimization and improvements
- logging clarity improvements
- improved test pattern list
- updated launch parameters with more options
- many many rewrites, code refactoring and such (better codebase structure, added frameworks for new features)

Here are some beautiful (?) screenshots of the board with bad TMU 1 RAM:

Wonderful job !
Could you provide a link for testing ?

SylvainA wrote on 2026-07-29, 01:20:

Could you provide a link for testing ?

New public release is not ready yet, it's coming. Probably soon (TM).
But work is being done on it.

Excited for this! Thanks!

Fagear wrote on 2026-07-29, 16:48:

New public release is not ready yet, it's coming. Probably soon (TM).
But work is being done on it.

😀

May I ask if there has been any further thought on support for the voodoo 1?

CRG wrote on 2026-09-23, 12:56:

May I ask if there has been any further thought on support for the voodoo 1?

Voodoo 1 probably has some hardware bugs in its silicon that prevent proper (write) operation from user-mode in Linux. Kernel module needs to be developed to work around those bugs.
Witchery project is on pause at the moment due to construction work at my place.

SylvainA wrote on 2026-05-30, 23:45:

FYI […]
Show full quote

FYI

The attachment 20260531_012718.jpg is no longer available

Try now to understand what that means 😀
I suppose to U13 memchip is dead ? R115 ?

Hello Sylvain, I am the author of this distro and the V2 TMU diagnose tool.
Sorry I totally missed your post.
The tool is playing various data pattern and configuration to try to guess the faulty part of your board.
Regarding your report, you should check the solder on the indicated pins.
The higher the score, the higer the fault probability.
Note that by defaut the tool stops searching at first faulty test.
You can try to make it continue using the '-c' flag (dont hesitate to use --help to get all possible flags).

You can PM me if you want (I am french btw 😉 )
++

chacha wrote on Yesterday, 19:24:

Hello Sylvain, I am the author of this distro and the V2 TMU diagnose tool. Sorry I totally missed your post. The tool is playin […]
Show full quote

SylvainA wrote on 2026-05-30, 23:45:

FYI […]
Show full quote

FYI

The attachment 20260531_012718.jpg is no longer available

Try now to understand what that means 😀
I suppose to U13 memchip is dead ? R115 ?

Hello Sylvain, I am the author of this distro and the V2 TMU diagnose tool.
Sorry I totally missed your post.
The tool is playing various data pattern and configuration to try to guess the faulty part of your board.
Regarding your report, you should check the solder on the indicated pins.
The higher the score, the higer the fault probability.
Note that by defaut the tool stops searching at first faulty test.
You can try to make it continue using the '-c' flag (dont hesitate to use --help to get all possible flags).

You can PM me if you want (I am french btw 😉 )
++

Hi! no problem dude.
Nice to talk to you, *bravo pour ton travail sur le logiciel* great job !
My problem on Maxi Gamer 3D² is solved.
Reflowing TMUs and FBI was already done, having checked all the resistors and resistor networks.
I first tried to reflow all the pin of U13 and checked all pad/vias from U13/pin 14 to R115 on the back, but no win 😒
I decided to swap U13 and solder brand new one.
I used heat gun to remove U13, strangely, C113 and C158 came off by themselves during pre-heating 😳.
I refitted U13 with my soldering iron to avoid extra heating, it was not easy to replace, and solder new C113 and C158.

After that, everything worked perfectly.
Now, the board is running in SLI with an identical matching board.

Thanks a lot fagear and chacha for your fantastic jobs !