Announcement

Collapse
No announcement yet.

PB 3.5 and NW-DOS, also PBINST problems

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Guest's Avatar
    Guest replied
    Anton,
    Thank you for your reply and your interest. I should make it
    clear that I am not accusing DR-DOS of being unstable, rather that
    the combination of DR-DOS and PB3.5 combined is unstable. The DOS
    is Novell NW-DOS 7 which I purchased about 3 years ago, and I have
    subsequently downloaded 7.02 and recently 7.03 from Caldera. All
    versions exhibit the same instability on both my machines, one is
    a 486/66 and the other is a pentium MMX 166. I might also mention
    here that I use a parallel-port Zip drive (100Mbyte), and the setup
    program for that - Guest.exe - does not work in Novell dos 7, but
    will work in 7.02 and 7.03.

    The PB source code is irrelevant, as the hang-ups happen in any code
    I happen to be working with, and the same code in PB under MS-DOS
    6.22 is rock stable.

    My usual setup in DR-DOS is a 7Mbyte cache (NWCache), with ram (96Mb) set
    up for both EMS and XMS, DPMI and DPMS enabled, and video memory
    switchable with MEMMAX.

    Anton, if you want to pursue this further, please use my email address
    <[email protected]> as we are wandering off topic with DR-DOS.

    regards, Colin D.


    Originally posted by Anton Lasich:
    Hi please send me an example of the offending code, your config.sys and autoexec.bat as well as a printout of the system.

    DR-DOS is "NOT" unstable. It is the software that is..reminiscent of the problems encountered with Windows 3.1 - remember - Microsoft said the General protedction faults were NOT there responsibility but that of the originating software...

    The issues around DR_DOS are complicated so I would like it very much if you would contact me - I represent the product here.

    Many thanks
    Anton Lasich
    [email protected]


    ------------------

    Leave a comment:


  • Guest's Avatar
    Guest replied
    Hi please send me an example of the offending code, your config.sys and autoexec.bat as well as a printout of the system.

    DR-DOS is "NOT" unstable. It is the software that is..reminiscent of the problems encountered with Windows 3.1 - remember - Microsoft said the General protedction faults were NOT there responsibility but that of the originating software...

    The issues around DR_DOS are complicated so I would like it very much if you would contact me - I represent the product here.

    Many thanks
    Anton Lasich
    [email protected]

    ------------------

    Leave a comment:


  • Guest's Avatar
    Guest started a topic PB 3.5 and NW-DOS, also PBINST problems

    PB 3.5 and NW-DOS, also PBINST problems

    There are two problems I haven't been able to solve since I
    bought PB3.5 for Dos. The first is that I cannot get Editor in
    PBINST to accept either F11 or F12 keys, whether by themselves
    or with Shift/Ctrl/Alt combinations. I also had this trouble
    with PB 3.2 as I recall However, when I take a look inside PBINST
    there is a section of code which appears to list all available
    key combinations, including F11 and F12 combos. Has anybody else
    had this problem, did you manage to fix it, and if so, how?

    The second is that I prefer to use NW-DOS/DR-DOS version 7 because
    of its ability to switch in video memory to extend the primary
    dos memory space, most useful when stepping larger programs, as
    well as its built-in networking capability. However, PB3.5 is
    quite unstable in this Dos, almost invariably crashing the computer
    (pentium 166)if I insert a program breakpoint or look at a variable
    value. Yesterday it crashed again after I set a breakpoint,
    causing loud banging noises from the hard drive and trashing the
    FATs, causing untold problems in salvaging my files. PB3.5 is
    quite stable under MS_DOS 6.22 and Win98, so I guess its a NW-DOS
    problem. Has anybody met this problem as well??

    Tech specs: Pentium MMX 166, 96 meg ram, set up as expanded and
    extended, with a 7-meg cache running. Disabling the cache does
    nothing to help.

    Woe is me. Colin D.
Working...
X