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.

😀