Hi!


I was attempting to completly remove the startup window as indicated in the manual

and had a few problems.

1) Could you add to the manual the following information ...This will help!


2) Starting with a previous working startup file,
I commented all lines inside brackets and got ERRNO #288.289


This procedure gave a message and also removed the acknex.wdf file, which gave me
the standard startup...not what I wanted.

3) I tried winstart with -diag and -nwnd


This works but now I can't read the acklog.txt file.
The .txt files takes a long time to show up on the screen and
when I try to open the acklog.txt file the message says ....There is a sharing violation....

4) So I tried


This works but :
a) There is a lag that is the same as the startup window ....so no suppressions of the start delay I guess.
and
b)
I still get the same message for the acklog.txt file. (sharing violation)


So I turned off my computer and found the following line in acklog.txt when I came back.


What is -ta

After testing

I have no startup window == ok
I have no suppression of the start delay
I still have the problem reading the acklog.txt file after playing my game.
and
I have no title in the title bar == bad for my game when reduced

Suppressing the startup window is described even with an example. The rest of the issues have nothing to do with the startup window.

In a PC under Windows, you can't open the same file for writing from different applications at the same time. You must terminate one application before the next one can open the file. But our manual is a Gamestudio manual after all, not a Windows manual. We can't cover all possible problems that can happen when working with files on a PC under Windows.

Hi JCL

Thanks for the answer.

The suppression of the startup windows works very well.
I like the manual.


I know that if a file is open under Windows it cannot be written to
by another application. In this case I did not have an open log file and
I was not attempting to write to it.
I believe that my game was closed.
I was only trying to open it to find out what the game was doing.

If the situation comes up again, I will recherche it and post in another section of the forum.

Thanks again

Normally problems with the log file are caused when the engine is not yet terminated when opening the log file.

The engine opens the log file for writing. When you open it in a text editor, it opens the file for writing also. This gives a conflict under Windows.

It can also happen when the engine does not close properly, but crashes, that the log file stays open. In this case you can only read it, f.i. with a text viewer, but not open it in an editor. This case is resolved by restarting Windows.

When will the ancient starter window system be overhauled? Wasn´t this on forecast once? It would be nice to have more options. For example creating a menu for setting graphics options like the resolution and so on. Or an easy way to change the application icon without having to use some resource hacker.

The starter system is for customized splash screens and start options only. A menu for setting graphics options should be done in lite-C. For creating an app icon you need a paint program, not a "resource hacker".

You mean with the Win32 API? That isn´t very user-friendly. You could provide a template for it.

Yes, I mean the Win32 API. We could provide a template, but that had to use the Win32 API also.