Pelles C forum

C language => User contributions => Topic started by: TimoVJL on December 07, 2025, 07:43:36 PM

Title: Vintage code
Post by: TimoVJL on December 07, 2025, 07:43:36 PM
TWinAT from 2005 and now compiled with Pelles c v13.
Sadly texts in Finnish language, as was created for company's IT persons.
Twenty years ago created and used until 2021 factory closed.

QuoteNetScheduleJobEnum function (lmat.h)

[NetScheduleJobEnum is no longer available for use as of Windows 8. Instead, use the Task Scheduler 2.0 Interfaces.
Title: Re: Vintage code
Post by: John Z on December 07, 2025, 09:48:23 PM
Not too sad though; can't let language be a a showstopper for a 'classic' :)

Here is the program translated to English for the C part and the .rc part.
Original Finnish version is still there, just 'excluded'.  To get that version
just 'exclude' the _EN versions and include the original as Timo adjusted for
Pelles C V13, then build again.


John Z
Title: Re: Vintage code
Post by: Vortex on December 08, 2025, 10:19:30 AM
Thanks, here are the error messages while trying to run the application on Windows 11 2024 H2 :

Conflicting i/o operation is running.
Error code : 50
Title: Re: Vintage code
Post by: John Z on December 08, 2025, 01:46:16 PM
Saw that too - here is what I found:

AI Overview
Error Code 50, "Conflicting I/O operation is running," usually means another process is using a disk/device, often seen with external drives on Mac (file system issues, sleep settings) or Windows (driver/network stack problems), or within apps like Steam (download conflicts)
. Solutions involve restarting the PC, running as administrator, checking/updating drivers, disabling antivirus, resetting network settings, or addressing specific file system/permission issues on Mac

For Windows Users (Event ID 50)

    Hardware Failure: Check system logs for underlying hardware issues (especially disk/network).
    Network/Driver Issues: Roll back network drivers or run network reset commands.
    Filter Drivers: Other software (antivirus, backup tools) can interfere; perform a clean boot (msconfig) to find the culprit.
----
Seems more likely that Windows has changed something from the 'good ole days' that now creates the error -

I did try many 'compatibility' modes in Win 11 24H2 to no avail.  Also tried as Admin - no improvement
Did not try disabling Antivirus yet though....

John Z
Title: Re: Vintage code
Post by: John Z on December 08, 2025, 03:08:58 PM
Well here is an/the issue -

C:\Users\John>AT
The AT command has been deprecated. Please use schtasks.exe instead.

The request is not supported.

C:\Users\John>

However AT /? still lists the old commands -

John Z
Title: Re: Vintage code
Post by: John Z on December 08, 2025, 04:23:15 PM
Update :

Runs just fine under windows 7 Home as well as Windows 7 Pro.

No errors, but I had nothing scheduled to see.

Run as ADMIN.

John Z
Title: Re: Vintage code
Post by: Vortex on December 08, 2025, 06:06:20 PM
The application works fine under Windows 7 Home Premium 64-bit.
Title: Re: Vintage code
Post by: TimoVJL on December 09, 2025, 02:27:41 AM
https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/at (https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/at)

There isn't remark of deprecated command, albeit command show it.
Title: Re: Vintage code
Post by: Vortex on December 09, 2025, 07:14:26 AM
Hi Timo,

As we know, the documentation of MS is not always correct.

C:\>ver

Microsoft Windows [Version 10.0.26100.7171]

C:\>at
The AT command has been deprecated. Please use schtasks.exe instead.