From: Rick Knight <rick_knight@rlknight.com>
To: Linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: Modem Problem
Date: Wed, 27 Oct 2004 10:26:50 -0700 [thread overview]
Message-ID: <417FDA5A.5010700@rlknight.com> (raw)
Claudia Neumann wrote:
> Am Mittwoch, 27. Oktober 2004 07:07 schrieben Sie:
>
>
>> ## Serial port settings
>>
>> # use e.g. "/dev/mouse", "/dev/ttyS0", "/dev/ttyS1", ...
>> # Note: all "/dev/ttyXX" may be suffixed by the IRQ
>> # used (instead of the default one), such as "/dev/ttyS2 irq 5"
>> # or "/dev/ttyS3 irq 9". Default: ""
>>
>> $_com1 = "/dev/ttyS0"
>> #$_com2 = "/dev/modem"
>> # $_com3 = ""
>> # $_com4 = ""
>>
>> # Lock directory (e.g. default: "/var/lock")
>>
>> # $_ttylocks = "/var/lock"
>>
>
>
> Where do you want to have the lock? To /var/lock? Delete the #.
> Do you have write permission for that directory?
> Or
>
> Put it to
> $_ttylocks = "$HOME/dosemu"
>
> Certainly you have write permission there.
>
> cu
>
> Claudia
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Claudia,
Thanks for your reply
The lock seems to be working properly and I do have write permissions to
/var/lock (its set to 777). Just for testing I did un-comment $_ttylocks
= "/var/lock" but that made no difference. I can start xdosemu and get
the DOS prompt, just as soon as I start my app (ProcomPlus) my system
freezes, keyboard and mouse are locked and a hard boot is required to
get things back. Any other suggestions?
Thanks again,
Rick Knight
next reply other threads:[~2004-10-27 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 17:26 Rick Knight [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 5:07 Modem problem Rick Knight
2004-10-27 11:36 ` Claudia Neumann
2004-10-27 17:31 ` Rick Knight
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=417FDA5A.5010700@rlknight.com \
--to=rick_knight@rlknight.com \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox