MSVC2022 Build

[soobidou]

I'm trying to use the driver in MBBS V10 and I tried to compile with MSVC2022 (using the provided SLN)

• I had to switch the "Active Solution Platform" to x86 as MBBSv10 is x86
• I ran the tests.exe to validate any issues
• Then I just backed up my original C:\BBSV10\WBTRV32.DLL and copied the new build in the folder
• Somehow that build won't start at all.

I also tried with another build (the one pasted by "Mark" on the MajorBBSv10 #development discord, no idea what was used to build that one).

When using that one, the BBS would start, you can spot new "db" files created as it initializes, but it "locks up" moments after logging in.

As per enusbaum comment, it seems BBSV10 worked with the driver, it could be a matter of using proper versions.

PS: Thanks for this driver, it's a great idea. Btrieve is a pain to toy around, and I can see several useful use cases for this!

[soobidou]

To better isolate the issue, I reinstalled the whole BBSV10 from scratch (TheMajorBBSv10_Beta_R32_Full.zip)
Using latest compiled wbtrv32.dll: SHA1 e7bb489de0925a743c5a21c86f6c577e10540fa1

I could start the BBS normally, DB files are created.

Then I disabled some non-necessary modules: Control, FU Globals, POP/NNTP, WL scheduler

It seems that disabling any module would create issues:

Or I randomly get this one and the BBS just dies

Note: It's not clear what triggers this error, but it looks like it's related to the action of disabling a module (any of them)

When this happen, the only way around is to replace WBTRV32.DLL with the original, load the BBS (using the DATs) shutdown, then
you can replace back the wbtrv32.dll with the new sqlite version.

[soobidou]

Can reproduce the issue at will, it looks related to any change in the enabled modules (both the action of enabling or disabling any module in WGSDMOD)
Doesn't seems related to any specific module per se.