General discussion

  • Creator
    Topic
  • #2080222

    Dos Vs Windows on Novell Network

    Locked

    by tinaa ·

    We are running a dos program on a novell Network. Whenever we run the portion of the program that Indexes the database from a dos computer or a computer booted to dos it takes about 8 hours to run.
    When the program is run from a computer that has windows and is run from a dos prompt thru windows it takes the same command about 20 minutes.

    Is there a setting I am missing somewhere?

All Comments

  • Author
    Replies
    • #3900770

      Dos Vs Windows on Novell Network

      by hcmartin ·

      In reply to Dos Vs Windows on Novell Network

      Sounds like a memory management issue. In DOS you need to set up our memory through the Config.sys and autoexec.bat files. Windows handles your memory for you when it’s running.
      Make sure your config.sys has
      dos=umb,high
      Device=A:\WINDOWS\Himem.Sys
      Device=A:\WINDOWS\EMM386.exe noems
      or a simular setup. Also try loading your program high. You can do this by a line in your autoexec.bat like
      LH programName.exe
      Also check your program for memory settings to be sure that it will take advantage of the extended memory.

    • #3902401

      Dos Vs Windows on Novell Network

      by aquarian ·

      In reply to Dos Vs Windows on Novell Network

      most DOS database functions are dependant on the memory settings in config.sys. Assuming you have a decent amount of memory (16Mb), I would suggest the following settings in your config.sys files:
      Files=40
      Buffers=60
      Stacks=9,256
      Adding / modifying these settings should help you greatly 🙂

      FYI, Windows9x only emulates DOS in a Windows shell. This means you are using the Win9x memory management, not DOS, unless you reboot into DOS mode. Good luck!

    • #3900308

      Dos Vs Windows on Novell Network

      by kenowsley ·

      In reply to Dos Vs Windows on Novell Network

      My assumption is that the database you are indexing is on the network, and that your Windows computers are using Client32. If this is true, then I’d assume your problem is related to the caching that happens automatically on the Windows workstation. Data is not actually written out to the server immediately under Windows with Client32. Rather, it is cached at the network card. So control is returned to OS sooner when data is cached. DOS doesn’t do this. You can simulate this on your windows machine by turning the TrueCommit property on. Do this and see what happens. It should be ungodly slow. Many database vendors want you to turn TrueCommit on if you are using their database on a Novell network. They do this because they think it will improve performance and/or prevent data corruption. But what it really does is completly degrade network performance. I don’t know if there is a caching version of the DOS redirector. You could see what Novell says.

    • #3793008

      Dos Vs Windows on Novell Network

      by tinaa ·

      In reply to Dos Vs Windows on Novell Network

      This question was auto closed due to inactivity

Viewing 3 reply threads