Image Map Image Map
Page 8 of 8 FirstFirst ... 45678
Results 71 to 79 of 79

Thread: Pc-mos/386

  1. #71
    Join Date
    Jul 2005
    Location
    United States
    Posts
    2,241

    Default

    There's no issue with screen shots and documentation but no code as long as its under copyright.

  2. #72
    Join Date
    Jul 2009
    Location
    Liverpool, NY
    Posts
    4

    Default

    I have a strange PC-MOS problem. I was running PC-MOS on a 486DX-100 supporting 3 Wyse terminals with no problems. It got hit by lightning so I copied all the data that I could from the HD, then did a clean install of PC-MOS 5.01 and copied back the saved files. Now I can't get PC-MOS to boot on any computer that I've tried. I have another portable system running an AMD K6-2 300MHZ and PC-MOS works just fine on there. I noticed that someone here said they couldn't get their PC-MOS to boot if they loaded the $386.sys driver. That seems to be where mine hangs too but then how do you get the multi-user function to work. Without the driver, my computer says "Not enough memory" for any tasks even though I'm running 64Mb. I ran this same system on the 486 with just 4Mb! Any ideas?

  3. #73
    Join Date
    Jul 2009
    Location
    Liverpool, NY
    Posts
    4

    Default

    Hi all, I have come up with a strange PC-MOS problem in just the last couple of days. Maybe someone here has a suggestion to fix it.
    I am presently running several small 2 and 3 user networks under PC-MOS 5.01, Clipper/Dbase III apps, a couple for 20 years and everything has been working fine. Suddenly PC-MOS will not open a .mem data file. In the last two days, four clients have called in with the same problem, on starting up their program, they get an error message saying. "Proc (module name) open error aucdata.mem (2) or (5). No matter which program module calls that file, it produces an error message.
    The same programs will run just fine under DOS 5.0 to Dos 6.22 except of course there is no multi-user ability.
    Any ideas?

  4. #74
    Join Date
    Aug 2012
    Location
    Jacksonville, FL
    Posts
    2

    Default

    I believe I may have a similar issue -- I find myself dealing with similar open error messages.
    The issue seems to have manifested on or about Aug 1st or 2nd, but was just brought to my attention late on the 3rd. It is affecting our ability to control some, but not all, aspects of an old paging terminal. I'll be taking my first serious look at it today, 8/7/12, but my initial quick "assessment" made Friday evening produced some results similar to your description. I will need to do some brushing up on the PC-MOS, DOS, and the paging terminal software before I can claim to make an actual evaluation, so it should be interesting and probably frustrating. I'll be watching to see what develops with your situation, and will try to report any progress I might make as well. Good luck.

  5. #75
    Join Date
    Dec 2007
    Location
    Edmonton AB
    Posts
    2

    Default

    Just discovered that the PC-MOS date generating function must not go beyond July 31 2012!! Came to work wednesday August 1st to discover crashed programs. ( PC-MOS / FOXPro 2.6 / SBT Accounting. ) Took several days to work this out. We managed to get our system running under MS-DOS 6 one user only. As work piled up, we tried to figure out why perfectly good files would not open once accessed or edited or copied (not a valid file, file not found, etc.), but were OK with DOS. It finally became apparent that the file header date was the problem. Like Y2K all over again. Any file with a 08/01/2012 date would not open under PC-MOS. The date was being written OK, but then the file would not open. Solution? spend $$$ to get an emergency upgrade to a whole new softawe/hardware system? ( Work still piling up with 12 person parts & equipment distribution business all trying to use one terminal!) Heres our solution... (1) Rewrite all affected files by editing the file header with a D-Base file-fix utility program and/or accessing & saving the files under MS-Dos booted up with an earlier system date. (2) Re-set the Computer C-mos clock date to the year 2000 and re-boot. (3) Insert a variable/function to add [365.25x10] days to all SBT accounting/inventory programs and procedure files anyplace a date is created/saved/displayd to make sure all "working" dates are correct. The files will still be written with old dates in the file header, but not an issue. Re-compile all program files, and re-index all data files to get "good" dates in FPX and CDX files. Booted up and everythig seems to be OK! Good to go for another 12 years, running 13 terminals/workstaions and 7 printers off one "server". Hope this helps any other PC-MOS cult users out there!
    Last edited by MDK; August 10th, 2012 at 04:19 PM.

  6. #76
    Join Date
    Aug 2012
    Location
    Jacksonville, FL
    Posts
    2

    Default

    MDK,
    Thanks. I had also made a contact in the digital paging world hoping to find anybody still running the same or similar equipment/software as we do, and got a reply indicating a Y2K-type issue also being experienced by other paging systems running PC-MOS. Although the fix/workaround is geared specifically to our paging systems' operation, the general procedure seems to be much like your solution:

    [courtesy of Brad Dye, brad@braddye.com]
    Hey Tom,

    Here are some e-mails about the Unipage Y2K-type bug from last week. The first is a bulletin that I sent out to my newsletter subscribers:

    > There is a Y2K type bug in the Unipage/Motorola Console 4. Evidently files updated with today's date, August 1, 2012, will cause some problems with accessing the database— like trying to do activations or swaps.
    > My limited understanding of the issue is that the files affected end ".DBF" and possibly others in the Console Database Program (CONDB.EXE) and changing the date to anything earlier should fix the problem.

    Then I received this:

    > Brad, thanks for the email, we were one of the carriers affected by this Unipage date issue. If it has value, thought I’d share the quick version of what we had to do. John B. with Microspace suggested that it would make sense to pass this along.
    > Our console system became unusable as a result of this 8-1-2012 date problem. However, the fix was not as simple as turning the clock back. Once we turned the date back to 2001 (the day of the week matches up), we were still getting condb40c.log file
    > errors & could not access subscriber information. The total fix was to use a MSDOS v6.22 boot disk. I could not modify bad files while running PCMOS os, which makes me suspect that PCMOS may be as much of a culprit as the console program. Next, edit
    > the condb40c.log file so it will have the 2001 modified date attached to it (all I did was change the last entry to a 2001 date). Then while in MSDOS, start the console program (condb) and invoke the “re-index database file” command under the maintenance
    > menu. This should be done for all databases that would be available under the log menu. At least, that worked for us.
    >
    > [...]

    I see you already developed a fix for your system, but perhaps it may be of some use to you or Paulsee, anyway. Had I not been fortunate enough to have received a specific fix for my issue, I'm sure I would have put yours to good use!! Thanks, and good luck.
    -Tom

  7. #77

    Default

    Quote Originally Posted by Paulsee View Post
    Hi all, I have come up with a strange PC-MOS problem in just the last couple of days. Maybe someone here has a suggestion to fix it.
    I am presently running several small 2 and 3 user networks under PC-MOS 5.01, Clipper/Dbase III apps, a couple for 20 years and everything has been working fine. Suddenly PC-MOS will not open a .mem data file. In the last two days, four clients have called in with the same problem, on starting up their program, they get an error message saying. "Proc (module name) open error aucdata.mem (2) or (5). No matter which program module calls that file, it produces an error message.
    The same programs will run just fine under DOS 5.0 to Dos 6.22 except of course there is no multi-user ability.
    Any ideas?
    You interest me strangely! What were these apps doing that operated under PC-MOS for the last 20 years? I used to work in the Digital Paging Industry, back then, and even sold an app to paging companies written in Clipper...

  8. #78
    Join Date
    Jul 2009
    Location
    Liverpool, NY
    Posts
    4

    Default

    Quote Originally Posted by Billyray View Post
    You interest me strangely! What were these apps doing that operated under PC-MOS for the last 20 years? I used to work in the Digital Paging Industry, back then, and even sold an app to paging companies written in Clipper...
    Hi Billy Ray,
    Strangely, eh? Well my particular apps are written for auction data management. I sell and support computer systems that are tailored specifically for auctioneers' sakes management. Yep, a couple of my systems have been in operation for over 29 years with a couple of updates and tweaks over the years as we come up with a beneficial improvement.

    Anyway, the Y2K type problem with PC/MOS is the date. Any date past July 31, 2012 will cause PC/MOS to act erratically and randomly reject any file with a date stamp later than 7/31/2012. I think that somewhere in the PC/MOS .exe file is a date stamp or reference to the end-date which if altered should cure the problem. So far, I haven't been able to find it.

    Someone suggested a hex editor but I haven't tried that yet. I used to be able to use a Norton utility program and search for a particular string within an .exe file and once found, edit the string but so far, not knowing what string I'm searching for, I have not been able to find it. Any suggestions in that area?

    I have been able to use a work-around for now but I sure would like to continue using PC/MOS just the way it has always worked before the bug problem.

  9. #79
    Join Date
    Jul 2009
    Location
    Liverpool, NY
    Posts
    4

    Default Re: Pc/mos bug

    OOOps, OOOps, the phrase "auctioneers' sakes management" should read "auctioneers' sales management"

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •