ovi,

Good to hear you got PADS2000 running in DOSBox. Congratulations!

I've always used OrCAD SDT386 and Capture for schematic capture, so I haven't seen that error message. However, I suggest you check the [cpu] section in dosbox.conf. It probably has core=auto:

[cpu]
# core -- CPU Core used in emulation: normal,simple,dynamic,auto.
# auto switches from normal to dynamic if appropriate.

# cycles -- Amount of instructions dosbox tries to emulate each millisecond.
# Setting this value too high results in sound dropouts and lags.
# You can also let DOSBox guess the correct value by setting it to max.
# The default setting (auto) switches to max if appropriate.

# cycleup -- Amount of cycles to increase/decrease with keycombo.
# cycledown Setting it lower than 100 will be a percentage.

core=auto
cycles=auto
cycleup=500
cycledown=20

(See: http://dosbox.sourceforge.net/wiki/index.php? … %2Fcore%2FIntro)

It sounds like DOSBox is switching the core to dynamic and that LOGIC2000 is doing something the dynamic core doesn't like. Try setting:

core=normal

and see if the problem goes away.

If so, you might want to make separate shortcuts to start PADS2000 and LOGIC2000. In the shortcut's property Shortcut / Target: use a command line option to start DOSBox with core=auto for PADS2000 and in the second shortcut for LOGIC2000 set core=normal. I think any option in dosbox.conf can be set with a command line option. That way you can use the dynamic core for PADS2000 to improve the speed, and still run LOGIC2000, although it will run slower with the normal core.

Read Chapter 3. Usage: in DOSBox's README.txt file for how to use command line options.

Hope that helps.

Hi thx for reply 😀
I have try to change the configuration from auto to normal in the core option but still comming the same error and logic2000 will not start 🙁
Regards
Ovi

I'm surprised it didn't make any difference. Looks like you're going to need the DOSBox Authors or an Oldbie to help.

In the meantime, try this experiment:

Download the official DOSBox v0.72 and run the installer to install it.
http://sourceforge.net/project/showfiles.php?group_id=52551

In the new DOSBox directory's .conf file, set

[dos]
xms=true
ems=false
umb=true

[autoexec]
mount c c:\pads
path=Z:\;c:\;c:\files;c:\cam;c:\lib;c:\logfil;
SET dosx=-swapdir C:\SwapFile
rem ** sets PADS Perform defaults **
SET PPCB=C:\;C:\FILES;C:\CAM;C:\LIB;C:\LOGFIL;
C:
cd C:\
del c:\SwapFile\P*.SWP

If LOGIC 2000 doesn't use the Phar Lap 386|DOS-Extender, set
ems=true

There won't be a [vga] or [parallel] section to set.

Start DOSBox v0.72 with a new but standard shortcut (don't change Start in:, leave it set for the new DOSBox directory).

Run PINSTALL.EXE and set the LOGIC 2000 graphic device to
640x480 IBM VGA Graphics Adapter.

Then try to start LOGIC 2000 and see if it will run that way or if you still get the same error.

So basically, you'll be checking to see if LOGIC 2000 will run in the latest official DOSBox v0.72 at 640x480.

[edit: safer mounting]

Um NEVER again suggest to somebody else to mount his whole c drive.

OK, but what's the problem with doing that? I've got my systems set up that way and I haven't had a problem.

Was discussed elsewhere already. If something goes wrong, you might
end up with corruption of files on your harddisk, thus limit the access.
If you do that, fine, your problem.

In my version of PADS Perform DOS v6.0.1, I have a version of the LOGIC program. The executable is called PLOGIC.EXE. I think this is about 2 or 3 versions newer than ovi's.

I ran the experiment I described in a previous post, running PLOGIC.EXE at 640x480 in DOSBox v0.72. The host OS is Win XP Pro SP2. I get the following results:

core=auto
ems=true or false

In the DOSBox Status Window, it says:
Exit to error: DynCore: illegal option in opcode 0xff

core=normal
ems=true or false

In the DOSBox Status Window, it says:
Exit to error: CPU:66:GRP5:Illegal call 7

In both cases, DOSBox closes a few seconds after displaying the above error messages. In the main DOSBox window, the program never appears to get started. After Enter is pressed, the cursor moves to the line below C:\PADS> plogic and into the 1st column (far left), then freezes.

I've never seen this and at this point, I have no idea what to do. We need professional help.

Try it with some debugger-enabled dosbox build (from the dev forum),
also maybe try loadfix.

In DOSBox v0.72 some internal commands only run from the C:\PADS> prompt if the full pathname is used for the command. This includes mem and loadfix. In HAL9000's build, they work from any prompt without a path.

In DOSBox v0.72, when I type loadfix or "loadfix plogic.exe" at the C:\PADS> prompt, I get

Illegal command: loadfix.

So I tried "z:\loadfix plogic" and "z:\loadfix -256 plogic" at the C:\PADS> prompt and loadfix ran and displayed
64 kb allocated. or
256 kb allocated.

Then the cursor moved to the line below and the far left column and then froze as before with the same messages in the Status Window. So loadfix doesn't seem to help.

I'll have to get a debugger build and try it later.

Include z:\ in your path override.

Not working i 'm getting the same error don't know what to do 🙁
Regards
Ovi

Yes, the z:\ worked. I had never had to use it in HAL9000's build so at first I didn't realize I had to put z:\ in the path= statement for other builds.

Now for the main subject. I downloaded the DOSBox 0.72 heavy debug version posted by Qbix. I installed it and left everything default except:

[log]
logfile=g:\temp\DOSBxDbg.txt

[dos]
ems=false

[autoexec]
mount (the usual way)
path=z:\;g:\;g:\pads;g:\pads\files;g:\pads\cam;
G:
cd G:\PADS
del g:\P*.SWP
del g:\PADS\SwapFile\P*.SWP

Then I ran PLOGIC.EXE at 640x480 as before, except with the Debug version. DOSBox closes in about 1 second, to quickly to see anything (quicker than the official DOSBox). It does create the logfile. I really don't know how to interpret it, but I noticed some lines stating things that look suspicious like:

14824131: BIOS:INT15:Unknown call 2403
14824218: DOSMISC:DOS:Multiplex Unhandled call 160A
14824224: DOSMISC:DOS:Multiplex Unhandled call 1600
14824230: DOSMISC:DOS:Multiplex Unhandled call 4680
14824280: DOSMISC:DOS:Multiplex Unhandled call ED00
14824287: DOSMISC:DOS:Multiplex Unhandled call ED00
14824294: DOSMISC:DOS:Multiplex Unhandled call ED00
14824301: DOSMISC:DOS:Multiplex Unhandled call ED00
14824308: BIOS:INT15:Unknown call BF02
14824319: DOSMISC:DOS:Multiplex Unhandled call A1FE
14824330: DOSMISC:DOS:Multiplex Unhandled call FBA1
14824338: DOSMISC:DOS:Multiplex Unhandled call F100

14824579: DOSMISC:DOS:Multiplex Unhandled call 1687
14824608: DOSMISC:DOS:Multiplex Unhandled call ED00
14824615: DOSMISC:DOS:Multiplex Unhandled call ED00

14855103: BIOS:INT15:Function 0x88 Remaining 0000 kb
14855457: BIOS:INT15:Function 0x88 Remaining 0000 kb

I've attached the logfile and the .conf file so that someone can take a look at it. If you want me to run this setup with specific options for the debugger, let me know the exact settings and I'll run it and post or attach the results. Remember, I've never run the debugger before, so be specific and detailed. Remember also that the online guide doesn't exactly match the 0.72 version. And, to appeal for more pity, remember that I'm doing this for someone else, not myself.

here is my log:

Is something i can do? Any Help?
Regards
Ovi

There's nothing wrong in the logs, so you'd have to debug the prog
in order to see what goes wrong.

Well now i have logic and pads running the solution wass just make a new config file from start and set core to normal , and also will like to say many thx to all for the help and suport
Regards
Ovi

Ps: here is my config if someone need it