forums.silverfrost.com

[Robert]

I wonder if users can try this example and see if it shows the select printer dialog when compiled with 64-bits.

[Kenneth_Smith]

/64 fails on my machine. Win32 OK

[Robert]

What does it do Ken?

[Kenneth_Smith]

[mecej4]

The 32- and 64-bit EXEs display a printer selection dialog.

Windows 64, no printer attached.

[Kenneth_Smith]

Robert,

After letting Windows Update do it's thing this morning:

2023-04 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5025239)

The code now runs as expected!

https://support.microsoft.com/en-gb/topic/april-11-2023-kb5025239-os-build-22621-1555-5eaaaf42-bc4d-4881-8d38-97e0082a6982

All the dlls referred to in the traceback above have been updated - since yesterday.

[Robert]

It seems to affect a lot of users. The VM I have it on is an old Windows 10 build so it isn't a transient issue.

[Kenneth_Smith]

No issues with the code on my older Windows 10 machine. Both before and after windows updates (not been turned on for a few months).

[Robert]

One thing which seem to provoke it is setting the default printer to 'Microsoft Print to PDF'

[IanLambley]

I now seem to be having this same problem. It prints to a printer, but when a PDF driver is selected, after it completes the output, it waits a few moments and then crashes with the following message:

Silverfrost 64-bit exception report on C:\Users\Ian\Documents\Projects\trunnion17\Debug\x64\Trunnion17.exe Thu Jan 1 00:00:00 1970


Unknown exception (80010012) at address 7fff0e819f0a

Within file KERNELBASE.dll
In RaiseException at address 8A
In RpcBindingToStringBindingW at address 3F0
Within file RPCRT4.dll
In RpcRaiseException at address 14
In InternalCStdIdentityGetIProxyManager at address 1CF6
Within file combase.dll
In NdrClientCall3 at address 581
Within file RPCRT4.dll
In WindowsCompareStringOrdinal at address 386
Within file combase.dll
In ObjectStublessClient32 at address 7E62
In CoWaitForMultipleHandles at address BFC
In HSTRING_UserMarshal64 at address DB8B
In HSTRING_UserMarshal64 at address CF99


RAX = 0000000000000000 RBX = 0000000000000000 RCX = 000000000d7df6b0 RDX = 0000000000000178
RBP = 0000000000000000 RSI = 0000000000000001 RDI = 0000000080010012 RSP = 000000002005ea10
R8 = 00007fff115d68c4 R9 = 0035002d00000002 R10 = 0000000000000000 R11 = 0000000000000000
R12 = 0000000025402318 R13 = 000000002005ecd0 R14 = 0000000000000005 R15 = 00007fff0f91c458

7fff0e819f0a) db 0f,1f,44,00,00

I'm not sure why it reports this as 1st January 1970.

The FTN95 version is:
Silverfrost FTN95/x64 Ver 9.10.4.0
I'm running Windows 11 Pro, Version 24H2

It happens whether I compile with Release, Debug or Checkmate.

[IanLambley]

Actually, it has just crashed for a normal physical printer as well.

[PaulLaidler]

Does it fail when using the old printer dialog?

Call USE_OLD_PRINT_DIALOG@(1) before SELECT_PRINTER@.

[IanLambley]

Yes, it still crashes

[PaulLaidler]

I don't get this failure on my machine so it looks like a Microsoft issue that only affects certain machines. (I am running Windows 11 24H2 and fully up to date.)

If the exception is "advisory" (i.e. recovery and continuation is possible without intervention) then we could provide a fix or a routine to call.

[IanLambley]

It is a very strange behaviour. After printing, it may or may not crash, but it definitely does with a pdf. The pdf is created and then a while later it just dies.

After last week, there are several men in white coats "Coming to take me away - Ha-haaa".

Help!!!