I noticed this morning my EDBMgr.Ini file was reset to only 4k and all of my session settings were gone. I don't know why. It would have helped a great deal if there was a .bak file or .bak2, .bak3 etc.. I had to restore the EDBMgr.ini file from a backup. Not everyone creates daily backups so they would really benefit from this.

Barry

Barry

>I noticed this morning my EDBMgr.Ini file was reset to only 4k and all of my session settings were gone. I don't know why. It would have helped a great deal if there was a .bak file or .bak2, .bak3 etc.. I had to restore the EDBMgr.ini file from a backup. Not everyone creates daily backups so they would really benefit from this.

I sort of think its a good idea but I'm not sure at which point it should be created and how many of them. I know they'd be small but I have a hatred of "unwanted" files cluttering up my disk.

Roy Lambert

<<
Barry wrote:
I noticed this morning my EDBMgr.Ini file was reset to only 4k and all of my session settings were gone. I don't know why. It would have helped a great deal if there was a .bak file or .bak2, .bak3 etc.. I had to restore the EDBMgr.ini file from a backup. Not everyone creates daily backups so they would really benefit from this.
>>

Sounds like good idea but in reality is actually tricky to get right. Assuming it uses TIniFile or such there is rarely any monolithic INi writing taking place so the challenge will be when to actually create the backup - it would have to be either on startup or maybe on shutdown.

I think if you can duplicate the actions that lead to the session info disappearing it might be something that can be addressed by itself. I definitely never had this happen so curious what caused it - having the INI separate from exe has definitely made it more pain to handle the ini (sharing them, backing them up etc).

Raul

Raul,

>Sounds like good idea but in reality is actually tricky to get right. Assuming it uses TIniFile or such there is rarely any monolithic INi writing taking place so the challenge will be when to actually create the backup - it would have to be either on startup or maybe on shutdown.<

I would vote for startup as long as more than one backup file is kept.

>I think if you can duplicate the actions that lead to the session info disappearing it might be something that can be addressed by itself. I definitely never had this happen so curious what caused it - having the INI separate from exe has definitely made it more pain to handle the ini (sharing them, backing them up etc).
<

This happened to me again today, what fun!

I have an external USB3 3TB Seagate drive I use for nightly backups with Acronis (Win7 64bit). This has been working fine for over a year. In the past couple of weeks the drive has been either disappearing or hanging the computer so that not even Alt-Ctrl-Del will work. Every application running at the time will then become disabled and display the wait icon, including EDBMgr if I happen to have it open. I suspect Win7 is trying to re-establish a hardware connection to the external USB drive and won't do anything until the connection is found. I have no idea why this external drive is now disappearing. Unplugging it and plugging it back in will not solve the problem. I switched from a USB3 port to USB2 port and late yesterday the same thing happened. The drive works fine for 6 hours or so, then disappears.

The only "solution" is to reset the computer. If EDBMgr is open when the computer is reset, the next time EDBMgr is run the EDBMgr.Ini file gets reset back to around 5k instead of its normal 500k and it has only the Default session in it.

For the time being I will unmount the drive when the computer boots and only have it mounted prior to doing a backup.

As far as the EDBMgr.Ini file is concerned, I can probably create a Windows scheduled task to copy the existing EDBMgr.ini file at computer shutdown and startup. That way I will have at least 2 files to choose from.

Barry

Giving it some further thought, I think the EDBMgr.Ini file problem can be solved simply by having EDBMgr close the EDBMgr.ini file after it has been written to. That way the file is not always open for writing and if the computer crashes or EDBMgr crashes, the EDBMgr.ini will remain intact.

Barry

Barry,

<< The only "solution" is to reset the computer. If EDBMgr is open when the
computer is reset, the next time EDBMgr is run the EDBMgr.Ini file gets
reset back to around 5k instead of its normal 500k and it has only the
Default session in it.  >>

That's corruption in the Windows file system that is causing such
truncation, so the only way around it is to create a backup of the .ini file
after modifications.

Tim Young
Elevate Software
www.elevatesoft.com

Barry,

<< Giving it some further thought, I think the EDBMgr.Ini file problem can
be solved simply by having EDBMgr close the EDBMgr.ini file after it has
been written to. >>

The EDB Manager *does* close the .ini file after every read/update.

Tim Young
Elevate Software
www.elevatesoft.com