[bobsedge]

Hello,

For a long-standing reason, I run two DOS programs I use regularly under Windows. For some unexplained reason, just a few days ago, after years of doing this, the programs are no longer accesible to me.

Clicking the long existing shortcut gives me an "attempt to access invalid address" message, and the file is identified as a .PIF file, which is new to me. Yet, when right clicking on the desktop shortcut - properties - program - it is still labeled as my long existing DOS .EXE program.

I didn't do anything different, didn't change anything intentionally; but maybe a Windows update messed it up. Don't have a clue. This problem surfaced with my Windows XP, which, of course, no longer (fully) supports DOS. But I have had the needed access via XP for years without a problem, until this week.

I still run this program under 98SE, on another computer, which, of course, will run DOS programs. I no longer use the 98SE computer on-line.

Help please!

Bob J.

[peterh40]

A PIF file (or Program Information File) was created as a shortcut to a older program file such as a DOS program back in Windows 3.1. It is the old equivalent of a shortcut or .lnk file now used on Windows 2000/XP/Vista machines and allows older programs to run on newer windows. In the PIF file you can specify memory requirements, whether windowed or full screen and so on.

[bobsedge]

Hello Peter,

Thank you for your quick reply.

I did know about using the old PIF file format under Windows, and my desktop shortcut may have been a .PIF, I'm not sure, but I had never received an "invalid address" message before, for both of these DOS programs.

My issue or problem is that access to these programs is now denied to me, after years of using it (them) several times a week.

I have no clue what may have changed, or how to re-gain access.

Thanks again,

Bob J.

[away22]

Bob,

This also just started happening to me today, with a DOS program I use that starts by using a PIF file.

After spending about 2 hours trouble shooting the problem, including running across your post describing the same problem, I determined the answer for my problem lies with an update I did in the last day or two to the Comodo software firewall program I run, to give me extra protection in addition to the hardware firewall in my router.

From reading posts on the Comodo forum a few minutes ago, I see that almost everybody who did this upgrade in the last few days, running DOS programs under XP, is having our problem.

There is a workaround which I learned from going to the Comodo forum; I'm sure they will release an update to the firewall program very soon, probably in the next few days. The workaround avoids having to uninstall the latest version of Comodo, just to access the DOS programs (which I would do "offline" when having Comodo disabled isn't risky, and which access to this DOS program is only 2 times a day).

I was really concerned I had a virus or some other malware. I hope your problem is solved as simply as mine. away22

[bobsedge]

Away 22,

Thank you!

That must be it!

I upgraded to the latest and greatest Comodo firewall version just a day or two ago, about when I lost access to my DOS programs.

I went through the Comodo forum discussion, but, short of removing the latest version, and downloading an earlier one (where would an older variant be available?), I wasn't sure what to do next. I played with some things, but my computer smarts still lie in the 1980s.

Hopefully, a corrective update is coming our way soon from Comodo.

Thanks again!

Bob J.

[away22]

Bob,No need to wait for a fixed version of the Comodo firewall to be released, or to uninstall the existing version and reinstall the previous version. Here's the workaround that I developed from reading posts on the the Comodo forum; it works perfectly for me and should for you too. There were other suggested ways on the Comodo forum to solve the problem but I chose the simplest one, since I don't believe it will take long for Comodo to issue a fix.There is a file that Comodo puts on your PC; its name is guard32.dll. You will find this file in the following path on your PC: c:\windows\system32\guard32.dll Comodo installs the file in another folder as well, but you want to work with the file it installs in the System32 folder. The guard32.dll file is the whole problem. The workaround is, for whenever you need to make your DOS programs work, is to either:A. temporarily change the name of that file, residing in the System32 folder, to something like guard32.old so it's inoperative,or, alternatively,B. temporarily move guard32.dll out of the System32 folder to some other easy to access place, such as your Desktop.However, PLEASE NOTE, that when you do A or B, above, as you prefer, then until you reverse A or B, as the case may be, Comodo will almost certainly not afford you the protection it is designed to give, and for that reason, to play it safe (even if you have a hardware firewall in your router), I would suggest trying to follow this 7-step procedure:1. go offline (i.e., disconnect your PC's "live" connection to the internet, so that you cannot get online), (Bob, you may have the version of Comodo that has an anti-virus component to it (I am using the old Internet only version of Comodo), which is all the more reason to be disconnected from the Internet while you're working with the DOS programs after having unloaded Comodo, as described in step #2, below).2. exit Comodo (right click on the Comodo icon in the system tray and chose Exit).3. perform step A or B, above, as you prefer, 4. work with your DOS programs and when you're through working with the DOS programs, 5. reverse step A or step B, as the case may be, 6. Start Comodo (start/programs/comodo/firewall) and finally,7. re-establish your internet connection and get Comodo's FULL protection, while you're doing everything else besides working with the DOS programs, being online at the same time.The 7-step procedure, above, should work to allow your DOS programs to work when necessary (albeit not while you are connected to the internet). This procedure, though inconvenient, works for me and should for you too. I would bet anything that before next weekend there will be a Comodo update fixing this problem. Write back if you need clarification, or if there's a glitch in my homegrown 7-step workaround procedure. To play it 100% safe, you should probably do a full backup of your PC first, before beginning to use the 7-step workaround procedure described above (admittedly, you're just manipulating one file but it never hurts to do a full backup, periodically).Good luck! Away22

[away22]

Administrator, I'm reposting since I can neither "edit" nor "delete" my post above, which does not recognize any of the paragraph returns that DO work in the message composing box, in which I am again composing this (repost) message. The paragraph returns also work in my clipboard window. I'm wondering if this problem is related to the maintenance that was done on the website last night. Away22

Bob,

No need to wait for a fixed version of the Comodo firewall to be released, or to uninstall the existing version and reinstall the previous version. Here's the workaround that I developed from reading posts on the the Comodo forum; it works perfectly for me and should for you too. There were other suggested ways on the Comodo forum to solve the problem but I chose the simplest one, since I don't believe it will take long for Comodo to issue a fix.

There is a file that Comodo puts on your PC; its name is guard32.dll. You will find this file in the following path on your PC:

c:\windows\system32\guard32.dll


Comodo installs the file in another folder as well, but you want to work with the file it installs in the System32 folder. The guard32.dll file is the whole problem.

The workaround is, for whenever you need to make your DOS programs work, is to either:

A. temporarily change the name of that file, residing in the System32 folder, to something like guard32.old so it's inoperative,

or, alternatively,

B. temporarily move guard32.dll out of the System32 folder to some other easy to access place, such as your Desktop.

However, PLEASE NOTE, that when you do A or B, above, as you prefer, then until you reverse A or B, as the case may be, Comodo will almost certainly not afford you the protection it is designed to give, and for that reason, to play it safe (even if you have a hardware firewall in your router), I would suggest trying to follow this 7-step procedure:

1. go offline (i.e., disconnect your PC's "live" connection to the internet, so that you cannot get online), (Bob, you may have the version of Comodo that has an anti-virus component to it (I am using the old Internet only version of Comodo), which is all the more reason to be disconnected from the Internet while you're working with the DOS programs after having unloaded Comodo, as described in step #2, below).

2. exit Comodo (right click on the Comodo icon in the system tray and chose Exit).

3. perform step A or B, above, as you prefer,

4. work with your DOS programs and when you're through working with the DOS programs,

5. reverse step A or step B, as the case may be,

6. Start Comodo (start/programs/comodo/firewall) and finally,

7. re-establish your internet connection and get Comodo's FULL protection, while you're doing everything else besides working with the DOS programs, being online at the same time.

The 7-step procedure, above, should work to allow your DOS programs to work when necessary (albeit not while you are connected to the internet). This procedure, though inconvenient, works for me and should for you too.

I would bet anything that before next weekend there will be a Comodo update fixing this problem. Write back if you need clarification, or if there's a glitch in my homegrown 7-step workaround procedure.

To play it 100% safe, you should probably do a full backup of your PC first, before beginning to use the 7-step workaround procedure described above (admittedly, you're just manipulating one file but it never hurts to do a full backup, periodically).

Good luck! Away22

[bobsedge]

Away22,

Great workaround!

And, it works!

Thanks so much for taking the time to set this up for me, and for re-posting your solution in a format which can be followed with ease.

Your input is greatly appreciated.

Bob J.

[away22]

Bob,

Am glad to hear the workaround was succesful in your situation.

I am very happy with Comodo and understand that sometimes there's a "hiccup" for the end-user, for non-beta software updates. Comodo has protected me well, so far, and so this minor hiccup doesn't faze me.

Take care. Away22

[away22]

Bob,

I just did a "manual" update check through Comodo (for me, after you open the program, I select the "Miscellaneous" tab, and then click on "Check for Updates").

I did this during a lull in my day, even though I am notified automatically of Comodo updates. In this case, my manually checking found an "update" before I was automatically notified by Comodo.

The new version is: 3.10.102363.531 and the best news is, the DOS program problem is cured, at least for me; that was fast! I hope this update cures the same issue on your PC. Away22

[bobsedge]

Hi,

Yesterday, I did the same thing - a manual check for a Comodo update. And, there it was, and, yes, I now have normal DOS access with their latest update.

They were quick!

Thanks again for your help,

Bob J.