Subject Re: Serious problem From Alex Safian <noway@noway.com> Date Tue, 26 Jan 2021 22:38:09 -0500 Newsgroups dbase.getting-started Gaetano mentioned the INI file problem. That's what it usually is for me when dBase crashes on startup. The easiest thing to do is just delete the INI file. On startup dBase will notice it's missing and will create a new one. If you have a lot of settings in the INI file that you don't want to lose you can try fixing it. This always works for me -- open the INI file in a good text editor like Notepad++ (Notepad will also work), go to the Navigator section and change Open, Minimized and Maximized all to 0, and look for any crazy values in Position -- like - 1000. Change the position numbers to something more moderate, like the Command Window Position probably has. dBase should then open normally with the Navigator window closed. Since this happens to me quite a bit for some reason I put a shortcut pointing to C:\Users\username\AppData\Local\dBASE  on the desktop right next to the dBase 2019 icon. I only went as far as dBase since I was running multiple versions for a while. Gaetano Wrote: > On 27/01/2021 6:34, Charlie wrote: > > Been running dbase for years and have not encountered this before...  Ran a program I had written and it would not finish the process.  So I went into dbase to test it further and found that dbase 10 ob windows 10 will not open for me.  Could this be due to corruption of a file?  This runs my business so it is very impotant I fix this fast.  Should I re-install dbase?  Not sure if I still have access to dbase 10...  Thanks for any help! > > > > There are many possible culprits... > > Try to explain more in detail: > > 1. do you get the splash screen? > 2. do you get an error message? > 3. did you change anything the machine? Install Windows update 2004? new > anti-virus? > > > As to the possible causes: > > 1. anti-virus - any change there recently? is dBase quarantined? Sophos > is known to cause issues. Recently, Bitdefender was blocking dBase > compiled apps for me, at first silently, so I had no idea what was going > on, so that\'s why it\'s important to check the quanrantine folder of your > AV and not rely on an AV message/warning. > 2. is there an instance of dBase hanging in the task manager? kill all > dBase instances in the task manager of Windows then try again > 3. some issue with your ini file (check under > C:\\Users\\Gaetano\\AppData\\Local\\dBASE\\Plus10\\Bin\\PLUS.INI, look at the > [Custom] section for unwanted entries (unlikely if this affects both a > compiled app and dBase, but worth a check) > 4. in the INI file, replace \"ErrorAction=4\" with \"ErrorAction=5\" so > dBase will write errors to a log file, then try again to restart dBase > and look if anything is logged in PlusErr.log (the default error log > file name) > 5. check the Windows event log (press the Windows Start key and type > \"Event\", select Event Viewer -- look in the Error and Warning sections > 6. DEP (Data Execution Prevention) can cause issues, but likely not from > one day to the next