ActiveState devkit was used to build the executable.
The file was a simple windows .txt file that contains license info. Subsequent to building the exe, the physical file was deleted. The file, not located in the VFS of the exe could be referenced using fileutil cat and the contents read,
fileutil writeFile was used to determine it was 'writeable', and the file was changed with the fileutil writeFile command, The file was read again and the new contents returned.
However, it does not seem the changes persist subsequent to exiting the app (ending execution).
Granted, this could be one of the dumbest questions ever asked. Alternatively, is is possible in any way to have an embedded app modify the exe in which it resides?
I don't know ActiveState devkit. A normal starkit can be unpacked and repacked with sdx. The file can be changed in between.roger that!
The Starpack FS is (effectively) a RO fs. I don't know if the VFS code returns
an error if writing is attempted or if the writing is dropped on the floor. It
might actually be a RW file system, but only to memory and not to the "backing
store" (the .exe file). Note: executable files are inheirently read-only (when
executed), so it probably makes no sense to file a "bug report" about this. If you need updatable persistance storage you will have to create and manage a
file on the end-users disk (eg whatever passes for a $HOME/.file under MS-Windows).
At Sat, 24 Jun 2023 11:30:43 -0700 (PDT) The Rickster <sled...@gmail.com> wrote:
ActiveState devkit was used to build the executable.
The file was a simple windows .txt file that contains license info. Subsequent to building the exe, the physical file was deleted. The file, not located in the VFS of the exe could be referenced using fileutil cat and the contents read,
fileutil writeFile was used to determine it was 'writeable', and the file was changed with the fileutil writeFile command, The file was read again and the new contents returned.
However, it does not seem the changes persist subsequent to exiting the app (ending execution).
Granted, this could be one of the dumbest questions ever asked. Alternatively, is is possible in any way to have an embedded app modify the exe in which it resides?
--The more I though about it; the more is suspected it was RO. The kicker was I got confirmation using the fileutils that it was writeable. And, logically those file are; the changes, however, are not persistent.
Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services
ActiveState devkit was used to build the executable.
The file was a simple windows .txt file that contains license info. Subsequent to building the exe, the physical file was deleted. The file, not located in the VFS of the exe could be referenced using fileutil cat and the contents read,
fileutil writeFile was used to determine it was 'writeable', and the file was changed with the fileutil writeFile command, The file was read again and the new contents returned.
However, it does not seem the changes persist subsequent to exiting the app (ending execution).
Granted, this could be one of the dumbest questions ever asked. Alternatively, is is possible in any way to have an embedded app modify the exe in which it resides?
Am 24.06.2023 um 20:30 schrieb The Rickster:Interesting...good to know I am not the only one with the need. Thanks. Was thinking about a 'modification' exe.
ActiveState devkit was used to build the executable.On the last TCL conference in Houston, there were some people with healthcare applications, which just did that: modify an exe with a
The file was a simple windows .txt file that contains license info. Subsequent to building the exe, the physical file was deleted. The file, not located in the VFS of the exe could be referenced using fileutil cat and the contents read,
fileutil writeFile was used to determine it was 'writeable', and the file was changed with the fileutil writeFile command, The file was read again and the new contents returned.
However, it does not seem the changes persist subsequent to exiting the app (ending execution).
Granted, this could be one of the dumbest questions ever asked. Alternatively, is is possible in any way to have an embedded app modify the exe in which it resides?
starpack within an update process.
It is a complex subject:
- the file storage format is called "metakit" by Jean-Claude Wippler.
There are RO and RW drivers for Metakit. Normally, only vlerq (the RO driver) is packed as package into the starkit, so no RW access.
- on many operating systems, a running exe file may not be modified
while running. So, you need a temporary "modification exe" which
modifies the target exe.
Or you can use TCL 9.0, which has the zip exe technology build in.
Be aware, that modifying a signed exe will make all virus scanner etc cry.
Hope this gives some pointers.
Take care,
Harald
On Monday, June 26, 2023 at 1:30:41 AM UTC-7, Harald Oehlmann wrote:
Am 24.06.2023 um 20:30 schrieb The Rickster:Interesting...good to know I am not the only one with the need. Thanks. Was thinking about a 'modification' exe.
ActiveState devkit was used to build the executable.On the last TCL conference in Houston, there were some people with
The file was a simple windows .txt file that contains license info.
Subsequent to building the exe, the physical file was deleted. The file, not located in the VFS of the exe could be referenced using fileutil cat and the contents read,
fileutil writeFile was used to determine it was 'writeable', and the file was changed with the fileutil writeFile command, The file was read again and the new contents returned.
However, it does not seem the changes persist subsequent to exiting the app (ending execution).
Granted, this could be one of the dumbest questions ever asked.
Alternatively, is is possible in any way to have an embedded app modify the exe in which it resides?
healthcare applications, which just did that: modify an exe with a
starpack within an update process.
It is a complex subject:
- the file storage format is called "metakit" by Jean-Claude Wippler.
There are RO and RW drivers for Metakit. Normally, only vlerq (the RO
driver) is packed as package into the starkit, so no RW access.
- on many operating systems, a running exe file may not be modified
while running. So, you need a temporary "modification exe" which
modifies the target exe.
Or you can use TCL 9.0, which has the zip exe technology build in.
Be aware, that modifying a signed exe will make all virus scanner etc cry. >>
Hope this gives some pointers.
Take care,
Harald
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 493 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 173:07:49 |
| Calls: | 9,704 |
| Calls today: | 4 |
| Files: | 13,736 |
| Messages: | 6,178,635 |