protel 99se windows 8 library file not recognized

#Protel 99se windows 8 library file not recognized 64 Bit#
#Protel 99se windows 8 library file not recognized full#

Then I tried the following and it seems to work! (for schematic) I tried many of the suggestions here but nothing worked. On my new laptop (WIN 8) I have the problem exposed in this thread. I have been using Protel since the version 1 (in DOS!) and I always bought the upgrades up to protel 99SE service pack3 I know this thread is a bit old but I think I have just found a workaround the problem! Now when I loaded the Schematic library, everything worked perfectly.ġ) The byte changes to NOP's worked perfectly for me with Protel 99 SP6.Ģ) The libraries need to be in the root directory of the library DDB and not in the documents folder. I went back and left the ones in the root directory alone but changed the files extension in the 'Documents' folder to. Now it loaded, but it loaded *both* copies and I had two of each Schematic library. So I moved copies of the Schematic libraries into the root directory of the DDB.

But when loaded the Schematic library, I got a message that said no libraries were present. When I loaded the PCB library, everything worked perfectly. Previously I had moved copies of the actual libraries to the root directory instead of the 'Documents' folder, but only in the PCB library. I found the bytes given in the two posts by Gunther VB and BonyBrown and made the changes to 0x90 (NOP).

#Protel 99se windows 8 library file not recognized 64 Bit#

I am running Win7 Professional 64 bit with Protel 99 SP6. I will do some more testing and - if necessary - tinkering if there are still more problems.

Save the changes, run Protel 99 SE, try loading a library, should work. Change all bytes from offset 2690E to 26917 (= a total of 10 bytes that need to be changed) to 90.Ī NOP instruction is 90 in hexadecimal, hence the change. So: get yourself a hex editor (I use 'HxD', it's free) and edit the 'Client99SE.exe' file. The call to SHGetPathFromIDListA does not do anything noteworthy, so I replaced all instructions related to that call with NOP instructions. The dialog gets confused and doesn't succeed in opening the file. But, a call to the windows function SHGetPathFromIDListA corrupts the memory where the filename is stored (it puts a zero where the string starts, which, in the null-terminated string world, means that the string is now suddenly empty).

#Protel 99se windows 8 library file not recognized full#

The library dialog tries to concatenate the filename and path of the selected library file to obtain a full path to the library file that you want to add. Ok, I just spent a long day debugging Protel 99 SE (Service Pack 6) in OllyDbg to solve the problem of not being able to load the library files in Windows 7 ('File not recognized').