zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) (10/26/88)
======= command failed =======
COMMAND: /bin/lmail 'jmsully' 'plocher'
======= standard error follows =======
======= text of message follows =======
>From admin!uport!uunet!umix!b-tech!zeeff
Received: by admin.UUCP (smail2.3)
id AA13024; 25 Oct 88 20:51:26 PDT (Tue)
Received: by uport.UUCP (smail2.5)
id AA08891; 25 Oct 88 20:52:18 PDT (Tue)
Received: from umix.UUCP by uunet.UU.NET (5.59/1.14) with UUCP
id AA14122; Tue, 25 Oct 88 12:11:14 EDT
Received: by umix.cc.umich.edu (5.54/umix-2.0)
id AA22755; Tue, 25 Oct 88 12:05:39 EDT
Received: by b-tech.ann-arbor.mi.us (smail2.5)
id AA00170; 25 Oct 88 12:03:18 EDT (Tue)
To: uport!plocher.uport!techs
Subject: Bug report for 3.0e ('386)
Message-Id: <8810251203.AA00170@b-tech.ann-arbor.mi.us>
Date: 25 Oct 88 12:03:18 EDT (Tue)
From: uunet!umix!b-tech.ann-arbor.mi.us!zeeff (Jon Zeeff)
These are the things that bother me the most:
1) Accessing /dev/lp while my HP Series II laser printer is off causes
/dev/lp to not work until I reboot (even after turning the printer on).
2) I can't run mkpart -A to add a bad sector without doing it from the
build disk.
3) Kermit.exe doesn't work under Dos Merge. Do you want a copy?
4) dBase II sometimes gets confused and ignores the assign command when
used under Dos Merge.
5) Mail to uport doesn't seem to work reliably.
6) I wasn't able to send mail via direct uucp connection to uport.
7) Directly attaching the lp port didn't seem to work at all under Merge.
8) News 2.11 compiled by gcc doesn't work quite right.
Suggestions:
Acks on reciepts of bug reports/mail would be nice.
Online Sys V.3 man pages as a standard item would be nice.
Pty support would be nice.
--
Jon Zeeff Ann Arbor, MI
umix!b-tech!zeeff zeeff@b-tech.ann-arbor.mi.ushsu@santra.HUT.FI (Heikki Suonsivu) (10/30/88)
In article <4893@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes: >3) Kermit.exe doesn't work under Dos Merge. Do you want a copy? On my 0.2 beta almost no serial communications don't work, including all versions of kermit I found, binkleyterm up from 1.4, SEAdog and some others. Opuscomm and bt 1.00 was the only combination which worked. >5) Mail to uport doesn't seem to work reliably. I have same problem. One message got through but it spent two(2) weeks on the trip and probably my other messages have disappeared, at least I haven't received any comments. I try once again and if it doesn't work then I post the buglist here, though my 2.2 is getting out-of-date already, but I would like to know if 3.0 has those problems solved. I'm in Europe so that might be causing some delay but 2 weeks is long time? Urgent question! Does 3.0 have lint2 compiled with reasonable table sizes, I run out of space on to my opinion quite small programs (~1 Meg of source code), or even better, dynamic tables! >7) Directly attaching the lp port didn't seem to work at all under Merge. I found out that /dev/lp0 is not lpt1: in my Olivetti M380C, I changed it to /dev/lp1 and then it worked. I don't know if this has anything to do with your problem but you might try fiddling around with different lp devices :-) >Online Sys V.3 man pages as a standard item would be nice. I miss them too! >Pty support would be nice. pick pty driver for unix-pc, it works.
scotty@l5comp.UUCP (Scott Turner) (11/01/88)
In article <4893@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes: >1) Accessing /dev/lp while my HP Series II laser printer is off causes >/dev/lp to not work until I reboot (even after turning the printer on). Well, you're one up on this site. Here the /dev/lp doesn't work at all... >2) I can't run mkpart -A to add a bad sector without doing it from the >build disk. This worked fine at this site from super user mode WHILE in multi-user mode. >7) Directly attaching the lp port didn't seem to work at all under Merge. This works fine here. We also have a 'pprint' program for use under unix that uses /dev/mem to do direct I/O port accesses to get bytes out the p-port. (Why the unix driver doesn't work is a mystery) >Suggestions: > >Acks on reciepts of bug reports/mail would be nice. With the lousy track record uport has at reliable mail delivery I'd say this would be REQUIRED not 'nice'. >Online Sys V.3 man pages as a standard item would be nice. YEAH! I've been looking for these guys since March '88. They're damn hard to come by. :( >Pty support would be nice. Comes with X-Windows. Scott Turner scotty@l5comp -or- uunet!l5comp!scotty
bill@twwells.uucp (T. William Wells) (11/02/88)
In article <4893@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
: To: uport!plocher.uport!techs
I think this address is wrong. It believe that it should be
uport!plocher.
: Subject: Bug report for 3.0e ('386)
: 2) I can't run mkpart -A to add a bad sector without doing it from the
: build disk.
It worked fine for me.
: 5) Mail to uport doesn't seem to work reliably.
I too have had some problems, but it appears to be a problem in
somebody's maps.
: 8) News 2.11 compiled by gcc doesn't work quite right.
How? It seems to work fine for me.
---
Bill
{uunet|novavax}!proxftl!twwells!billzeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) (11/02/88)
In article <16939@santra.UUCP> hsu@santra.UUCP (Heikki Suonsivu) writes: > >>Pty support would be nice. > >pick pty driver for unix-pc, it works. I suspect that you are referring to the '286 Unix, where they do work. I tried two versions of the PD pty code on the '386 Unix and neither worked. -- Jon Zeeff Ann Arbor, MI umix!b-tech!zeeff zeeff@b-tech.ann-arbor.mi.us
pjh@mccc.UUCP (Pete Holsberg) (11/03/88)
What about /dev/lp in V386 2.2? Does yours work? Mine doesn't.
--
Pete Holsberg UUCP: {...!rutgers!}princeton!mccc!pjh
Mercer College CompuServe: 70240,334
1200 Old Trenton Road GEnie: PJHOLSBERG
Trenton, NJ 08690 Voice: 1-609-586-4800kjk@pbhyf.PacBell.COM (Ken Keirnan) (11/03/88)
In article <378@mccc.UUCP> pjh@mccc.UUCP (Pete Holsberg) writes: > >What about /dev/lp in V386 2.2? Does yours work? Mine doesn't. > The "/dev/lp" entry comes linked to "/dev/lp0". Try, in turn, outputing a string (like "echo Hello there") to /dev/lp1 and /dev/lp2. You may be suprised when one of these work (then again, maybe you won't :-)). Then just link the /dev/lpx that worked to /dev/lp. Please refer all questions to Microport - I don't have the answer :-). -- Ken Keirnan - Pacific Bell - {att,bellcore,sun,ames,pyramid}!pacbell!pbhyf!kjk San Ramon, California kjk@pbhyf.PacBell.COM
zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) (11/03/88)
In article <134@twwells.uucp> bill@twwells.UUCP (T. William Wells) writes: >In article <4893@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes: >: To: uport!plocher.uport!techs > >I think this address is wrong. It believe that it should be >uport!plocher. Without a doubt. It left here as uport!techs uport!plocher. >: 2) I can't run mkpart -A to add a bad sector without doing it from the >: build disk. > >It worked fine for me. Uport admits that it's a problem. Usually you can't boot after using mkpart on a running system. >: 8) News 2.11 compiled by gcc doesn't work quite right. > >How? It seems to work fine for me. I got some rare errors with rnews failing. I didn't have a chance to pin it down though. The cc version works fine. -- Jon Zeeff Ann Arbor, MI umix!b-tech!zeeff zeeff@b-tech.ann-arbor.mi.us
john@jetson.UPMA.MD.US (John Owens) (11/03/88)
In article <4154@pbhyf.PacBell.COM>, kjk@pbhyf.PacBell.COM (Ken Keirnan) writes: > The "/dev/lp" entry comes linked to "/dev/lp0". Try, in turn, outputing > a string (like "echo Hello there") to /dev/lp1 and /dev/lp2. In case anyone wonders what's behind this: Parallel ports on PCompatibles typically use one of three I/O port base addresses: 03BC, 0378, and 0278 (hex). The ROM BIOS searches for parallel ports at these three addresses, and places the ones it finds, in order, in a table in RAM. The first one it finds becomes LPT1 (as referred to by DOS), the second one LPT2, and the third LPT3. So if you only have one printer port, it will always be LPT1 under DOS. The microport drivers (apparently) and the SCO Xenix drivers have lp0, lp1, and lp2 always associated with the three fixed port addresses. I like the microport/Xenix way myself, but I tend to keep track of which ports my cards are on. I suppose the way the BIOS (and therefore DOS) does it is better for people who don't. -- John Owens john@jetson.UPMA.MD.US uunet!jetson!john +1 301 249 6000 john%jetson.uucp@uunet.uu.net
kjk@pbhyf.PacBell.COM (Ken Keirnan) (11/05/88)
In article <165@jetson.UPMA.MD.US> john@jetson.UPMA.MD.US (John Owens) writes: [ stuff deleted ] >Parallel ports on PCompatibles typically use one of three I/O port >base addresses: 03BC, 0378, and 0278 (hex). The ROM BIOS searches >for parallel ports at these three addresses, and places the ones it >finds, in order, in a table in RAM. The first one it finds becomes >LPT1 (as referred to by DOS), the second one LPT2, and the third LPT3. >So if you only have one printer port, it will always be LPT1 under >DOS. > >The microport drivers (apparently) and the SCO Xenix drivers have lp0, >lp1, and lp2 always associated with the three fixed port addresses. I >like the microport/Xenix way myself, but I tend to keep track of which >ports my cards are on. I suppose the way the BIOS (and therefore DOS) >does it is better for people who don't. > This would certainly explain why some people with 386 DOS Merge 1.1 have a tough time trying to use "direct attachment" of the parallel printer port. Microport has 3 entries in /etc/dosdev for direct attachment of a parallel port: lpt1, lpt2 and lpt3 which correspond to the three *common* address for DOS LPT1/2/3. It appears that direct attachment may have to be achieved using "+alpt2" or "+alpt3" depending on the address used by the specific hardware. Actually, it may be more convenient, and certainly less confusing, to change the /etc/dosdev entry(ies) to correspond to the way DOS sees the printer port(s) for a particular system. Has anyone done this? If so, does it function correctly? Ken Keirnan -- Ken Keirnan - Pacific Bell - {att,bellcore,sun,ames,pyramid}!pacbell!pbhyf!kjk San Ramon, California kjk@pbhyf.PacBell.COM
hsu@santra.HUT.FI (Heikki Suonsivu) (11/05/88)
In article <378@mccc.UUCP> pjh@mccc.UUCP (Pete Holsberg) writes: > >What about /dev/lp in V386 2.2? Does yours work? Mine doesn't. Try linking it to /dev/lp1 or /dev/lp2 instead of /dev/lp0 which is in distribution (or whatever it was, wasn't the correct one for me).
hsu@santra.HUT.FI (Heikki Suonsivu) (11/05/88)
In article <4907@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes: >In article <16939@santra.UUCP> hsu@santra.UUCP (Heikki Suonsivu) writes: >>pick pty driver for unix-pc, it works. > >I suspect that you are referring to the '286 Unix, where they do work. I >tried two versions of the PD pty code on the '386 Unix and neither worked. The version I picked up from comp.sys.att works both in my Convergent Tech Miniframe and Microport 386 Unix. I dont think I had to change it at all or something really minor, I can remember that I got it working easily. There was another one which came from comp.sources.*, that one didn't work at all in neither miniframe nor 386.
bill@twwells.uucp (T. William Wells) (11/07/88)
In article <4910@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
: >: 2) I can't run mkpart -A to add a bad sector without doing it from the
: >: build disk.
: >
: >It worked fine for me.
:
: Uport admits that it's a problem. Usually you can't boot after using
: mkpart on a running system.
So, one should run mkpart -A only when running single user?
If so, it really looks like I'm going to have to bring my system down
periodically. First, to check for bad blocks (I'm paranoid) and second
to fix the inode problem with news.
I believe the right way to do this kind of thing is this:
1) add a cron entry to go to some unused init state
2) add an inittab entry to start a script to do single-user
maintenance
3) have that script return to init state 2 at the end
Does that sound right?
: >: 8) News 2.11 compiled by gcc doesn't work quite right.
: >
: >How? It seems to work fine for me.
:
: I got some rare errors with rnews failing. I didn't have a chance to pin
: it down though. The cc version works fine.
What are the symptoms of rnews failing? I haven't seen that happen,
but I'll keep my eyes open if I know what to look for.
---
Bill
{uunet|novavax}!proxftl!twwells!billplocher@uport.UUCP (John Plocher) (11/07/88)
+---- In <152@twwells.uucp> T. William Wells writes: | +---- In <4910@b-tech.ann-arbor.mi.us> Jon Zeeff writes: | | 2) I can't run mkpart -A to add a bad sector without doing it from the | | floppy | +---- | Uport admits that it's a problem. Usually you can't boot after using | mkpart on a running system. +---- Version: Microport V/386 Version 3.0e (fixed in 3.0e.1) If You have a drive with more than 17 sectors per track (RLL or ESDI) and you run mkpart -A while rooted off of the hard disk then The boot code on your hard disk is replaced with an incorrect version and you won't be able to reboot from the hard disk (but the disk isn't damaged and your data is safe) Symptom: boot: /unix Results in a "Can't find /unix" message Cause: The boot image in /etc/boot on the hard disk is the one from 2.2 which only understands 17 sectors per track; the one on the floppy is the correct one from 3.0e, which was rewritten to handle variable numbers of sectors per track. Fix: Boot from the build disk Run fsck on the hard disk "fsck /dev/dsk/0s1" Mount the hard disk "mount /dev/dsk/1s0 /mnt" If you ran mkpart & overwrote your boot code, re run it "/etc/mkpart -f /mnt/etc/partitions -B /etc/boot disk0" Copy the correct boot image to your hard disk "cp /etc/boot /mnt/etc/boot" Unmount the hard disk "umount /dev/dsk/1s0" Reboot off of the floppy -John Plocher Microport Customer Support
zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) (11/08/88)
In article <256@uport.UUCP> plocher@uport.UUCP (John Plocher) writes: >+---- >Version: >Symptom: >Cause: >Fix: Thanks for the fix. Now if we could just get you to post these things as soon as you know about them instead of waiting until we run into them and have to solve them ourselves ... -- Jon Zeeff Ann Arbor, MI umix!b-tech!zeeff zeeff@b-tech.ann-arbor.mi.us
bill@twwells.uucp (T. William Wells) (11/10/88)
In article <256@uport.UUCP> plocher@uport.UUCP (John Plocher) writes: : +---- In <152@twwells.uucp> T. William Wells writes: : | +---- In <4910@b-tech.ann-arbor.mi.us> Jon Zeeff writes: : | | 2) I can't run mkpart -A to add a bad sector without doing it from the : | | floppy : | +---- : | Uport admits that it's a problem. Usually you can't boot after using : | mkpart on a running system. : +---- : If : You have a drive with more than 17 sectors per track (RLL or ESDI) : and you run mkpart -A while rooted off of the hard disk The attributions above are a little wrong: the "Uport admits" is Jon Zeef. However, John's message explains why I got away with mkpart -A: my drive has only 17 sectors per track. Lucky me! --- Bill {uunet|novavax}!proxftl!twwells!bill