The Major BBS Forums

Microsoft 10 Pro 32-Bit Operating System, X64 based Processor Build Number 17763.1577.

ptaylor2 wrote:
> Microsoft 10 Pro 32-Bit Operating System, X64 based Processor Build Number
> 17763.1577.

and i assume major bbs 10? i will install a copy on a vm and play with it and try to duplicate your crash.

Windows or pkunzip.exe?

ptaylor2 wrote:
> Windows or pkunzip.exe?

im gonna install a major bbs v10 setup in a vm and try to find out why ctrl-v is crashing. i run a modified
core v3.12 that is frontloaded with too many changes to upgrade my own system but i got a vm setup so i
can help sysops debug.

daniel_spain wrote:
> ptaylor2 wrote:
> > I am running windows 10 32 bit and pkunzip is located in the wgserv
> > directory and it runs fine.
>
> what ver you running?

Are you asking what vesion of Pkunzip or Windows pelase?

PKUNZIP (R) FAST! Extract Utility Version 2.04g 02-01-93

Hi, Dan. Another V10 Sysop has tested the CTRL-V issue and can confirm the crash. Is it possible that a more recent version of pkunzip would fix this? Or perhaps making a pkunzip.bat and tricking it into using infozip or something else? I'm curious if you can solve this, because as far as I can tell, there is no way to disable or lock out with keys the option to view file contents.

BlaZ

BlaZ wrote:
> Hi, Dan. Another V10 Sysop has tested the CTRL-V issue and can confirm the
> crash. Is it possible that a more recent version of pkunzip would fix
> this? Or perhaps making a pkunzip.bat and tricking it into using infozip
> or something else? I'm curious if you can solve this, because as far as I
> can tell, there is no way to disable or lock out with keys the option to
> view file contents.
>
> BlaZ

so all ctrl-v does is utilize "pkunzip -v <filename>" now removing pkunzip altogether could cause other issues down the road but i see no reason the v10 distro cannot be modified to utilize a level 4 option in the file libs configs for

enter the program name used to view the contents of a file when invoking the control-v command.

CTRLVNAM {7zip} S 20 Archive viewing program name

enter the command line used by the program set forth in the level 4 option CTRLVNAM
that will view the contents of a file.

CTRLVCMD {-v} S 20 Archive viewing command line

then within the file library code simply:

sprintf(tmpbuf,"%s %s %s",ctrlvnam,filename,ctrlvcmd);

now send tmpbuf

this is exactly how i enabled smarthost authentication back in 2013 i just added in my own options for SMTP AUTH

i am assuming it is a 64bit compatibility issue with this particular ver of pkunzip or no? i could see if it is strictly within v10 or any wg system within a 64 env

BlaZ wrote:
> Hi, Dan. Another V10 Sysop has tested the CTRL-V issue and can confirm the
> crash. Is it possible that a more recent version of pkunzip would fix
> this? Or perhaps making a pkunzip.bat and tricking it into using infozip
> or something else? I'm curious if you can solve this, because as far as I
> can tell, there is no way to disable or lock out with keys the option to
> view file contents.
>
> BlaZ

i am actually working on this as we speak. gonna try a few diff things with the obvious choice being a
long term answer over a work around. will let ya know.

This isn't specific to a 64-bit OS... only specific to V10. I'm running Win10-32, and the original sysop who reported the bug is also running 32-bit Windows 10. I'm not sure what broke it, because 3.2 or 3.3 on Windows 10 doesn't crash with CTRL-V. Let me know what you figure out.

I will also take a look at it