• Please review our updated Terms and Rules here

Any way to bypass a password login in CompuPro Concurrent DOS?

Al Kossow said:
could someone put a zip of all of the extracted files somewhere?
Click to expand...

Here you go: https://drive.google.com/file/d/15B9WO8Radt6O5-9b7-Inec8VRSnMCq7N/view?usp=sharing

Those are the ones I extracted directly from the disks with the exception of the files I mentioned in the post above, which were instead extracted from the disk images by Larry K. I believe out of the ones that had errors copying, the ones in the disk images are probably the more accurate copies of the two (although I still can't be 100% sure they are correct).
 
Well it's kinda rough but I got Concurrent DOS 4.1E to fire up on my CompuPro. It boots on 8" floppy with the Quantum Q540 hard disk driver.
Yes CCPMF85.SYS is corrupt so went with CCPM340.SYS. I don't know what it's complaining about with the M: drive, I do have two working M-DRIVE cards.
I don't see the file UTMP.DAT on the disk images. I might try to do a GENCCPM but without a manual I'm flying blind. Is anyone aware of a Concurrent DOS 4.1 manual for CompuPro?
It's not the same as for IBM PC/XT. I had to cobble this photo to get it to upload. Oh, it's running on multiple terminals ... Larry G
CDOS 4.1.JPG
 
retrogear said:
Well it's kinda rough but I got Concurrent DOS 4.1E to fire up on my CompuPro. It boots on 8" floppy with the Quantum Q540 hard disk driver.
Yes CCPMF85.SYS is corrupt so went with CCPM340.SYS. I don't know what it's complaining about with the M: drive, I do have two working M-DRIVE cards.
I don't see the file UTMP.DAT on the disk images. I might try to do a GENCCPM but without a manual I'm flying blind. Is anyone aware of a Concurrent DOS 4.1 manual for CompuPro?
It's not the same as for IBM PC/XT. I had to cobble this photo to get it to upload. Oh, it's running on multiple terminals ... Larry G
View attachment 61629
Click to expand...

I'm glad it's at least somewhat functional!

I think I am going to try to put together a Greaseweazle and get flux images of these disks -- I am curious to see whether the greater detail produced by a flux image would help me 'repair' the disks.

There were a handful of manuals in the box these disks came in, but none of them were for the CompuPro stuff (there was one for WordStar, one for the terminal that the owner of the disks was using, one for a printer, and oddly, one for a sewing machine).
 
Last edited:
There are several places where you can find the manual for CompuPro CDOS 3.1, which is similar enough to version 4.1 to allow you to get by. Herb Johnson's retrotechnology site does not list a copy of the 4.1 manual either, but it does list a copy of the CompuPro CDOS 5 manual. I do have a print copy of the CDOS 4.1 manual, and scanning it is on my very long list of "to do" things.

CDOS automatically uses any MDRIVE cards it finds in your system as hard drive buffer space. Since you don't have a DISK3 hard drive system, the MDRIVE error you are seeing may represent a side effect.

In a previous post it was mentioned that MEM.CON is one of several corrupt files in the distribution you are working with. MEM.CON is an essential software component required by GENCCPM to build CCPM.SYS. I currently have my system in a state of disarray while working on another project, otherwise I'd pull the files you are missing for version 4.1 (like CCPMF85.SYS) off my master disks and upload them for you.



retrogear said:
Well it's kinda rough but I got Concurrent DOS 4.1E to fire up on my CompuPro. It boots on 8" floppy with the Quantum Q540 hard disk driver.
Yes CCPMF85.SYS is corrupt so went with CCPM340.SYS. I don't know what it's complaining about with the M: drive, I do have two working M-DRIVE cards.
I don't see the file UTMP.DAT on the disk images. I might try to do a GENCCPM but without a manual I'm flying blind. Is anyone aware of a Concurrent DOS 4.1 manual for CompuPro?
It's not the same as for IBM PC/XT. I had to cobble this photo to get it to upload. Oh, it's running on multiple terminals ... Larry G
Click to expand...
 
>I have uploaded the CDOS 4.1D version of CCPMF85.SYS

Thank you. That will help. I am familiar with CDOS 3.1. That's the system I currently have and just bought the masters off ebay. Since the 4.1 disks were shared here I thought I'd give it a try.
There are differences I don't recognize. I do have a DISK3 system which currently boots CDOS 3.1DM. I just am doing 4.1 by boot floppy to try things out.
 
retrogear said:
I am familiar with CDOS 3.1. That's the system I currently have and just bought the masters off ebay. Since the 4.1 disks were shared here I thought I'd give it a try.
There are differences I don't recognize. I do have a DISK3 system which currently boots CDOS 3.1DM. I just am doing 4.1 by boot floppy to try things out.
Click to expand...

My understanding is that CDOS 3 provided features compatible with MSDOS 1.x, whereas CDOS 4 provided features compatible with MSDOS 2.x. CompuPro made many changes of their own to the XIOS between versions, including support for a few new hard drive models among other things.
 
floppy boot is working now, the corrupt ccpmf85.sys is about 6K shorter.
>My understanding is that CDOS 3 provided features compatible with MSDOS 1.x, whereas CDOS 4 provided features compatible with MSDOS 2.x.
Actually with CDOS 3.1D, I have a 5.25 on CompuPro that can read MSDOS disks. My path is USB flash thru Win98 to 360K 5.25 then to CompuPro. The CompuPro drive is 96tpi 720K so can only read msdos, not write so my return path is CompuPro CDOS 720k 5.25 read by 22DISK using COM4 definition on a 1.2M HD 5.25" then Win98 back to usb flash. Quite the round trip ...
I just discovered that if the CDOS 4.1 boot floppy contains a file named BANNER it gets displayed on the slave monitors during boot. These are things a manual would tell me. This does not occur in 3.1D.
>this has been listed for a while now
>https://www.ebay.com/itm/Compupro-X1...t/202774968623
I know, I've been watching it. $75 is a little steep for that. I have source code but the 5.25" support was added at the end and there is some errors. I wonder if that's what is on that disk for sale.
I always need to patch the step rate for my 8" drive. I don't know where the step rate patch is for 4.1 so I'm using my patched 3.1 loader and it seems to work ok.

Larry G
 
CompuPro CDOS 4.1 MSDOS support includes the ability to designate one of the logical hard drive partitions as an MSDOS partition, including the DOS 2.x tree directory structure. This allows some MSDOS programs that need to make use of the MSDOS tree directory structure to run from a hard drive under CDOS 4.1. Files can be freely copied (PIP'd) between the CP/M and MSDOS hard drive partitions.

Unfortunately CompuPro CDOS 4.1 file transfer with PCs via floppy disk still required use of the NEWMEDIA utility found in version 3.x. CompuPro finally built that support directly into the OS when they developed CDOS 5.x, which can read and write all MSDOS floppy media (1.2M and 360K 5.25", and 3.5") in addition to CompuPro's CP/M formats for 8" and 5.25" disks. CDOS 5.x is the version I have been using for many years.

Unless you really want to stay with CDOS 3.x now that you have a copy of CDOS 4, I don't think the $75 that eBay seller is asking for that copy of the CDOS 3.x XIOS source is worth it. CompuPro provided just enough XIOS source with 4.x to allow for making changes you would ever want to make so that you can assemble a new XIOS and GENCCPM a new CCPM.SYS. There are many changes (eg floppy drive step rate, floppy drive assignment, console port, and terminal definitions) that you can make without having to reassemble the XIOS in CDOS 4.x. Run the command "CDOSINST" followed by the name of your CCPM.SYS file - that will bring up a menu of items you can edit directly in the CCPM.SYS file. Unfortunately CompuPro never made available the source for its LOADER files for any version of CDOS, but presumably the LOADER files they provided had the floppy drive step rate configured so that even the slowest drives would still work to bring up the system.

retrogear said:
floppy boot is working now, the corrupt ccpmf85.sys is about 6K shorter. Actually with CDOS 3.1D, I have a 5.25 on CompuPro that can read MSDOS disks. My path is USB flash thru Win98 to 360K 5.25 then to CompuPro. The CompuPro drive is 96tpi 720K so can only read msdos, not write so my return path is CompuPro CDOS 720k 5.25 read by 22DISK using COM4 definition on a 1.2M HD 5.25" then Win98 back to usb flash. Quite the round trip ...
>this has been listed for a while now
>https://www.ebay.com/itm/Compupro-X1...t/202774968623
I know, I've been watching it. $75 is a little steep for that. I have source code but the 5.25" support was added at the end and there is some errors. I wonder if that's what is on that disk for sale.
I always need to patch the step rate for my 8" drive. I don't know where the step rate patch is for 4.1 so I'm using my patched 3.1 loader and it seems to work ok.
Click to expand...
 
Last edited:
hmb said:
CDOS 5.x is the version I have been using for many years.
Click to expand...

Would it be possible for you to get me copies of your 5.X disks or files? I'd particularly love to see what the boot track looks like for a 5.25" floppy, if your boot sectors were generated from within CDOS 5.X that is.
 
jmetal88 said:
Would it be possible for you to get me copies of your 5.X disks or files? I'd particularly love to see what the boot track looks like for a 5.25" floppy, if your boot sectors were generated from within CDOS 5.X that is.
Click to expand...

I may be able to do better than that. A few weeks ago I ran across a set of three 5.25" CompuPro CDOS 5.0 master disks I received a long time ago. What is odd (to me) about the disks is that the LOADER files don't have the standard set of CompuPro file names I am used to seeing and they don't work on my standard CompuPro computer. The CCPM.SYS files provided don't work either. I suspect what I am looking at is a set of disks intended to be used with the CompuPro 10+. The only reason I haven't already sent them to you is because I currently don't have a setup that allows me to create disk image files so that you can recreate a boot disk. I could upload the individual files though.

If you already have a disk image for any CompuPro 5.25" boot disk, its boot track should look very similar across all OS versions. Often the boot loader for an older CompuPro OS version will work with a subsequent OS version. However even CompuPro's boot loaders are of course very hardware specific, which is where you run into trouble because the hardware configuration of a 10+ is different from their S100 based systems.
 
hmb said:
I may be able to do better than that. A few weeks ago I ran across a set of three 5.25" CompuPro CDOS 5.0 master disks I received a long time ago. What is odd (to me) about the disks is that the LOADER files don't have the standard set of CompuPro file names I am used to seeing and they don't work on my standard CompuPro computer. The CCPM.SYS files provided don't work either. I suspect what I am looking at is a set of disks intended to be used with the CompuPro 10+. The only reason I haven't already sent them to you is because I currently don't have a setup that allows me to create disk image files so that you can recreate a boot disk. I could upload the individual files though.

If you already have a disk image for any CompuPro 5.25" boot disk, its boot track should look very similar across all OS versions. Often the boot loader for an older CompuPro OS version will work with a subsequent OS version. However even CompuPro's boot loaders are of course very hardware specific, which is where you run into trouble because the hardware configuration of a 10+ is different from their S100 based systems.
Click to expand...

Oh, that would be great!

The only boot image I have that kind of works is a CCPM image that I think linked to earlier in the thread, but it seems like it's slightly too old for my particular variant of the 10+. My system tries to execute the code but then freezes. The reason I suspect the boot track of being an issue is because it never moves the head off track 0 - it just executes the code in track 0 then lifts the drive head, becoming unresponsive. I am assuming since my hard drive had CDOS 5.0 on it that if I had boot disks of that particular version, they would work.

I do have a working setup that should be able to image the disks -- I don't know if you would be interested in sending them to me to image and then having me send them back? I understand if you don't want the disks to get damaged or lost in the mail, though (and shipping to/from Canada might be expensive anyway). If it helps, the setup that worked best for me (I tried a couple of different machines) was using my Zenith 386 with a Teac FD-55GFR and IMD or Teledisk.
 
jmetal88 said:
My system tries to execute the code but then freezes. The reason I suspect the boot track of being an issue is because it never moves the head off track 0 - it just executes the code in track 0 then lifts the drive head, becoming unresponsive. I am assuming since my hard drive had CDOS 5.0 on it that if I had boot disks of that particular version, they would work.
Click to expand...

Those symptoms are pretty typical of having a loader that is not correct for your system's hardware configuration.

Having followed your saga from the beginning of this discussion, it seems pretty clear that the crucial information the CompuPro hard drive controller needs to obtain from the first several physical sectors of your hard drive has been wiped out. Since at this point it is likely you will need to reformat the hard drive, the exact version of CDOS you use probably doesn't matter too much. However, if you ever get CDOS 5.x running it will be great. CDOS 5.x in my opinion was the best CompuPro OS ever. CompuPro CDOS v5 runs CP/M-80, CP/M-86, and some MSDOS software and and can transfer files using many CP/M format disks (8" and 5.25") and every MSDOS 5.25" and 3.5" format. CompuPro did move on to release CDOS v6 and CDOS386 up to a v3, but by then it was clear they were pursuing the PC market and it became less straight forward to transfer files using legacy CP/M floppy formats.
 
hmb said:
Those symptoms are pretty typical of having a loader that is not correct for your system's hardware configuration.

Having followed your saga from the beginning of this discussion, it seems pretty clear that the crucial information the CompuPro hard drive controller needs to obtain from the first several physical sectors of your hard drive has been wiped out. Since at this point it is likely you will need to reformat the hard drive, the exact version of CDOS you use probably doesn't matter too much. However, if you ever get CDOS 5.x running it will be great. CDOS 5.x in my opinion was the best CompuPro OS ever. CompuPro CDOS v5 runs CP/M-80, CP/M-86, and some MSDOS software and and can transfer files using many CP/M format disks (8" and 5.25") and every MSDOS 5.25" and 3.5" format. CompuPro did move on to release CDOS v6 and CDOS386 up to a v3, but by then it was clear they were pursuing the PC market and it became less straight forward to transfer files using legacy CP/M floppy formats.
Click to expand...

Well, regardless, I need a floppy with a compatible boot loader before I can even attempt to reformat my hard drive, and so far I have not found one. I am really hoping that such a loader resides on one of your 5.0 disks!
 
Al Kossow said:
I bought a later 10+ with a SASI disk that should be here this week.
[/url]
Click to expand...

You got a very nice system - seems to have been well looked after. Like all of CompuPro's systems, it is ruggedly manufactured.
Although the seller couldn't get a sign-on message on a connected terminal, that may just be related to having incorrect hardware handshaking or communications settings on the terminal, or not having the terminal connected to the serial port designated for the user console. I'm optimistic you will be able to get it up and running but if not, hopefully the disk images (once I make them) will help.
 
Hmb just came through with the disk images and they boot! I'm so excited to finally be able to use this machine!
 
You must log in or register to reply here.
Back
Top