• Error Code 64

    From IB Joe@1:275/312 to All on Sun Aug 1 11:47:54 2004
    Hello everybody.

    I have been trying to make the change from DOS to OS2 and I'm getting an odd error with FE right now. When I fo to run fesetup or fesetup2 it doesn't load and exits with an error 64...

    it'll toss & scan mail as stuff comes in... I just can't access feutil and make
    any changes.

    is there a quick fix for this or is it a fresh install??

    Thanx

    IB

    ---
    * Origin: Joe's Computer, Crystal River, Fl USA telnet.joesbbs.com (1:275/312)
  • From Paul Quinn@3:640/384 to Ib Joe on Mon Aug 2 16:29:00 2004
    Hi! IB,

    In a message to All you wrote:

    I have been trying to make the change from DOS to OS2 and I'm getting
    an odd error with FE right now. When I fo to run fesetup or fesetup2
    it doesn't load and exits with an error 64...
    it'll toss & scan mail as stuff comes in... I just can't access
    feutil and make any changes.
    is there a quick fix for this or is it a fresh install??

    I don't know what this error #64 is. You might like to re-visit "FESetup -R<n>,<a>", though. See page #9 of the dox. A fresh install is a real PITA. I hope it helps.

    Cheers,
    Paul.

    --- Radius 4.010-2004/04/21_Beta
    * Origin: Dammit! I wanna be _their_ aliens. (IP 1200-1500 UTC) (3:640/384)
  • From IB Joe@1:275/312 to Paul Quinn on Mon Aug 2 08:52:20 2004
    Hello Paul.

    I might have to do a fresh install... no matter what I do with fesetup I get that error... :(

    02 Aug 04 15:29, you wrote to me:
    I don't know what this error #64 is. You might like to re-visit
    "FESetup -R<n>,<a>", though. See page #9 of the dox. A fresh install
    is a real PITA. I hope it helps.

    IB

    ---
    * Origin: Joe's Computer, Crystal River, Fl USA telnet.joesbbs.com (1:275/312)
  • From Mike Luther@1:117/3001 to Paul Quinn on Mon Aug 2 11:10:10 2004
    Joe ..

    I have been trying to make the change from DOS to
    OS2 and I'm getting
    an odd error with FE right now. When I fo to run
    fesetup or fesetup2
    it doesn't load and exits with an error 64...
    it'll toss & scan mail as stuff comes in... I just can't access
    feutil and make any changes.
    is there a quick fix for this or is it a fresh install??

    One of the critical things which you need to watch in using any DOS application
    in OS/2 is the whole cadre of DOS specific stuff that can be adjusted for each and every DOS application that you run under an OS/2 DOS-VDM. OS/2 has a default cadre of these decisions and parameters which it uses that is combined with AUTOEXEC.BAT for DOS-VDM applications. When you run a DOS-VDM as a Desktop or a command line application, whatever,you'll get this default parameter group and will run the AUTOEXEC.BAT which is the default one supplied
    with OS/2.

    But wait! There's more! (Lots more!)

    You can and often must customize the way OS/2 presents the DOS operating system
    differently for lots of programs! And more interesting, when you set up a DOS-VDM for FE or IM or OPUS or BINK or whatever, you'll typically be involved with at variation of not only a specific .BAT file that application lives in, but it also runs AUTOEXEC.BAT at the start, just like you would if you fired up
    a complete box for DOS. Aha! You'll find these parameters in the Program Properties folder for any given DOS-VDM and you get to them via the Session's tab in that folder where you click on DOS Properties and then on, in the first look at this, ALL DOS settings.

    If you ain't been here before, welcome to the really wonderful world of DOS under IBM's OS/2. As you first toggle through them all, if you have never been
    here before, you'll be astounded. For one thing, you normally create a completely unique AUTOEXEC.BAT file for this application and give it a unique name. Say FEXEC.BAT, whatever. Then, starting with a copy of the OS/2 standard AUTOEXEC.BAT, you create all the needed paths, environment,and whatever for this application. Then you go into the Dos Settings tab and you specify that you want FEXEC.BAT instead of AUTOEXEC.BAT. But wait,there's more! Here are the DOS Settings I'm using, but be aware, I'm also using Ray Gwinns wonderful COMM drivers! If you are using IBM's COMM drivers your display will be different for the COMM drivers and you will have to adjust them
    to the same profile as I have for Ray's stuff:

    AUDIO_ADAPTER_SHARING : None
    DOS-AUTOEXEC : MAILEXEC.BAT
    DOS-BACKGROUND_EXECUTION : ON
    DOS_BREAK : OFF
    DOS_DEVICE: : C:\OS2\MDOS\ANSI>SYS
    C:\SIO2K\vx00.sys (Ray's drivers)
    C:\SIO\x00.sys e b,1,38400
    DOS_FCBS : 32
    DOS_FCBS_KEEP : 16
    DOS_FILES : 50
    DOS_HIGH : ON
    DOS_LASTDRIVE : Z
    DOS_RMSIZE : 640
    DOS_SHELL : (Leave at default)
    DOS_STARTUP_DRIVE : (Blank)
    DOS_UMB : ON
    DOS_VERSION : (Leave at default)
    DPMI_DOS_API : ENABLED
    DPMI_MEMORY_LIMIT : 16
    DMPI_NETWORK_BUFF_SIZE : 8
    EMS_FRAME_LOCATION : AUTO
    EMS_HIGH_OS_MAP_REGION : 0
    EMS_LOW_OS_MAP_REGION : 384
    EMS_MEMORY_LIMIT : 8192
    HW_NOSOUND : ON
    HW_ROM_TO_RAM : ON
    HW_TIMER : OFF
    IDLE_SECONDS : 60
    IDLE-SENSITIVITY : 99
    INT_DURING_IO : OFF
    KBD_ALTHOME_BYPASS : OFF
    KBD_BUFFER_EXTEND : ON
    KBD_CTRL_BYPASS : NONE
    KBD_RATE_LOCK : OFF
    MEM_EXCLUDE_REGIONS : (Blank)
    MEM_INCLUDE_REGIONS : (Blank)
    MOUSE_EXCLUSIVE_ACCESS : OFF
    PRINT_SEPARATE_OUTPUT : ON
    PRINT_TIMEOUT : 15
    SESSION_PRIORITY : 1
    VIDEO_8514_XGA_IOTRAP : ON
    VIDEO_FASTPASTE : ON
    VIDEO_MODE_RESTRICTION : NONE
    VIDEO_ONDEMAND_MEMORY : ON
    VIDEO_RETRACE_EMULATION : OFF
    VIDEO_ROM_EMULATION : ON
    VIDEO_SWITCH_NOTIFICATION : OFF
    VIDEO_WINDOW_REFRESH : 1
    VSIO2K_CtlsFlowControl : ON
    VSIO2K_ReceiveXonisFlowControl : OFF
    VSIO2K RTSisFlowControl : ON
    VSIO2K SentXonisFlowControl : OFF
    XMS_HANDLES : 32
    XMS_MEMORY_LIMIT : 2048
    XMS_MINIMUM_HMA : 0

    Then, with a TEXT editor that does *NOT* add an EOF mark at the end of your CONFIG.SYS file for this OS/2 box, go in and make sure the following lines are either there or are added just before your line BASEDEV=IBMKBD.SYS:

    REM ** Determines if foreground apps have priority access to disks.
    REM ** YES is default. If applications need equal access, change NO.
    REM ** Comm apps need this to NO.
    REM PRIORITY_DISK_IO=YES
    PRIORITY_DISK_IO=NO

    REM ** Lets computer continue boot on non-fatal boot run errors
    PAUSEONERROR=NO

    REM ** forces computer to deliver system error to the application direct.
    SET AUTOFAIL=YES

    REM ** Set to allow kill from the WPS hold CTRL key when touch WPS.
    SET SCKILLFEATUREENABLED=1

    REM ** Many complex DOS programs need more than 20 **
    FILES=50
    SET SHELLHANDLESINC=30

    And in the area in CONFIG.SYS around your MDOS\COMMAND.COM line do this:

    REM ** Identifies and loads DOS command processor COMMAND.COM
    REM ** /p switch keeps the command processor in memory until shutdown.
    REM SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS **** ORG
    SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /e:2048 /p

    REM ** Tells DOS how many FCBS to be open at once and minimum left open.
    REM FCBS=16,8
    FCBS=32,16

    REM ** Sets the amount of memory available for DOSs use, maximum 640K.
    RMSIZE=640

    Your replacement for AUTOEXEC.BAT must have the correct path for all the FE application directory in it. I've been running 1.46 in DOS-VDM's for years this way just fine,


    Sleep well; OS/2's still awake! ;)

    Mike @ 1:117/3001

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)
  • From Rich Wonneberger@1:2624/50 to Ib Joe on Mon Aug 2 21:06:14 2004
    *** Quoting Ib Joe to All dated 08-01-04 ***
    I have been trying to make the change from DOS to OS2 and I'm getting
    an odd error with FE right now. When I fo to run fesetup or fesetup2
    it doesn't load and exits with an error 64...

    Ib,

    Does the partition that FE is installed on have more then 2 gig of free space??
    You might need a program s/a 2gbfix.com.
    I thought this only fixes DOS programs that have problems if there is more then 2 gig of free space.

    Long shot??
    Rich
    I-Net turtil@frontiernet.net


    ... Excuse me, can you spare a tagline?
    ---
    * Origin: Turtil's Pond BBS. Monroe NY 845-783-2106 (1:2624/50)
  • From mark lewis@1:3634/12 to Mike Luther on Mon Aug 2 21:40:20 2004
    DOS-AUTOEXEC : MAILEXEC.BAT
    DOS-BACKGROUND_EXECUTION : ON
    DOS_BREAK : OFF
    DOS_DEVICE: : C:\OS2\MDOS\ANSI>SYS

    is that a mistype or ?? it should be ansi[dot]sys ;)

    )\/(ark


    * Origin: (1:3634/12)
  • From Mike Luther@1:117/3001 to Mark Lewis on Mon Aug 2 22:52:28 2004
    You are correct Mark!

    DOS-AUTOEXEC : MAILEXEC.BAT
    DOS-BACKGROUND_EXECUTION : ON
    DOS_BREAK : OFF
    DOS_DEVICE: : C:\OS2\MDOS\ANSI>SYS

    is that a mistype or ?? it should be ansi[dot]sys ;)

    Should be a 'dot' there. Sorry.

    In that I don't know what the error 64 means, what I was trying to do was to do
    an end run around the DPMI, and extended plus expanded mem manager stuff,as well as to cover the possible path statement not being in the environment. That, plus lack of available file handles, and kept ones and so on, can creat a
    lot of hard to find error causes in DOS-VDM's in OS/2.

    Beyond those issues, I've long ago learned to expand the environment beyond even 768 bytes as I posted. Who knows what that setup program is doing relative to internal 'unseen' shell statements? (!). I sure don't, but I know that from a compiler standpoint, I can sure create a shell-child game that the user doesn't really know is being used. Thus if there isn't enough environment
    space, or the path isn't really passed to whatever is made of this, all kinds of wierd errors can happen.

    There are some other very oblique errors in OS/2 and DOS-VDM's as to box lockups and so on that I doubt very seriously are involved at this initial stage of troubles. These have to do with MULTIPLE DOS-VDM's on an OS/2 box in the Fix Pack 15 range and on into early Fix Pack 16 officially. Somehow, in the upgrade work of the OS/2 game from Warp 4.5 into the 'unified' kernel of what is now MCP1/2 and specifically Fix Pack 17, DOSCALL1.DLL turned up a problem wherein the environment wasn't passed totally correctly between NESTED use of batch files! If you look at this whole thing as it really is, when you use a .BAT file in a DOS-VDM, even that first use of AUTOEXEC.BAT is, really, a
    nested batch file! There were, at this time major issues in how the HPFS file system and its write caching code were getting lost as to the operating path between batch files and on collapse of one, such as AUTOEXEC.BAT and the one you would be running.

    It took a SUBSTANTIAL amount of work and hand plugging of all my many, many batch and .CMD files that wrote a cross-section trace log for each step of every .BAT and and .CMD file, on this multiple BBS/TCP-IP/TELNET server box here. But I proved exactly how and at what time in relation to the cache writing, and particularly, the refresh of the OS2.INI files, the information it
    took to get IBM's kernel crew to get this whole mess fixed. The DOSCALL1 and other code data to fix this wasn't found and completed until Fix Pack 16.
    Plus a portion of the DHCP log-in code was creating multiple falsely held open, same-name file handles, for each renewal of DHCP post boot-up. That wasn't finally found and fixed by IBM until not many months ago even well beyond the UN2206 and WR08706 level fixes! In other words, some of this which can produce these strange errors in DOS-VDM's in OS/2 wasn't really cleaned up until AFTER the MCP2 and even XCR0002 official releases were made.

    This is one reason I keep trying to get people to officially update to the very
    latest IBM fixes and so on. Even my Fix Pack 16 boxes didn't stabilize out until after some of the post fixes were made! Plus .. Fix Pack 17 is another major effort to equalize the operating code between the old Warp 4.52 and MCP kernel and PMMERGE level stuff. It is really needed for those wanting stability in DOS-VDM work. At least on heavy multiple DOS-VDM boxes with lots of DOS still running, it seems to be here.

    That said, another thing we learned was that it is really better still to do the batch file game in a .CMD file, even though a lot of it may be actually running DOS programs as components of the native OS/2 .CMD file!!

    Once done, the entire system here which is still running FE 1.46 under DOS,and IM and a FAMILY and thus OS/2 mixed operation for 1:117/100 and as well two other OS/2 BBS units, POTS and TELNET for 1:117/3001, plus a full FTP server and two RF packet gateway applications in DOS-VDM's .. FINALLY stabilized out.
    It finally guit throwing everything from FE errors on to totally locked box stuff. Actually, one of the TNC RF programs is a WIN 3.1 proggie that runs on top of everything else! In fact, to keep FE even running, until all the IBM stuff came clean, I had to deliberately turn off the HPFS Lazy Write cache game
    to keep from box lockups every week or so.

    Since I dunno what Error 64 really is .. all I was doing was trying my best to
    be of service. Trying to pay back some of the really thoughtful and real debug
    time that IBM spent with me officially on finding and fixing some of this stuff
    on DOS-VDM's. I'm *VERY* happy with IBM and what they have been able to do for
    little old me. I really respect them.


    Sleep well; OS/2's still awake! ;)

    Mike @ 1:117/3001

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)