From: Ulrich Hansen <my.gr...@mailbox.org>

--===============0481829807500901100==
Content-Type: multipart/alternative;
        boundary="Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36"


--Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
        charset=utf-8


> Am 13.02.2017 um 06:19 schrieb Dan Schmidt <helpdesk...@gmail.com
<mailto:helpdesk...@gmail.com>>:
>
> I hope I am not committing the dreaded "forum necromancyrCL

I had to look that uprCa I really liked the picture of the ghoul in the first
google result :-))

> but I thought I might document that the 386 version, combined with the
mentioned "reset" trick, has solved my issues with ssh2dos stability, thank you
for the idea.

Congratulation! But as I see it, it was your idea all along.
>
> Also, quick type-o - "I am not sure why you would want to run SSH in DOS in
VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all
strange.

WellrCa It kind of IS strange. ;-) The reason is simple: I have a bit time to
kill at the moment, so I was taking another look at my
VirtualBox/FreeDOS/Networking images I started a few years ago at
https://www.lazybrowndog.net/freedos/virtualbox/
<https://www.lazybrowndog.net/freedos/virtualbox/>. I updated them to FreeDOS
1.2 and was checking if everything still works as expected. And well, SSH2DOS
wasnrCOt and I was unable to find a fix. So thank you again for your help!

At the moment IrCOm updating the MS Client pages (sigh).



> Am 13.02.2017 um 06:19 schrieb Dan Schmidt <helpdesk...@gmail.com>:
>
> I hope I am not committing the dreaded "forum necromancy" but I thought I
might document that the 386 version, combined with the mentioned "reset" trick,
has solved my issues with ssh2dos stability, thank you for the idea.
>
> Also, quick type-o - "I am not sure why you would want to run SSH in DOS in
VirtualBox"  I did not mean to imply that running Dos on VirtualBox is at all
strange.
>
> On Mon, Jan 30, 2017 at 9:35 PM, Dan Schmidt <helpdesk...@gmail.com
<mailto:helpdesk...@gmail.com>> wrote:
> I didn't try the 386 version, perhaps that will be more stable.  Also, if you
type "reset" before exiting, you can avoid "missing dos screen."  (IE - the
crash every time I exited)
>
> Ulrich, my friend, I am not sure why you would want to run DOS in VIrtualBox
on a MacBookPro, but I am glad I could help you.  :-)  Years ago, several other
technicians laughed at me when I bought an old Pentium for $5 saying"You can't
do anything with that!" FreeDos helped me prove them wrong.
>
> On Sat, Jan 28, 2017 at 8:02 AM, Ulrich Hansen <my.gr...@mailbox.org
<mailto:my.gr...@mailbox.org>> wrote:
>
>> Am 28.01.2017 um 06:23 schrieb Karen Lewellen <klewel...@shellworld.net
<mailto:klewel...@shellworld.net>>:
>>
>> To answer your question for myself, I never have this issue.  No crashes,
and i  can spend hours working on line.  Further I have done more than my share
of downloads with sftpd386 as well.
>
>
>> On Fri, 27 Jan 2017, Dan Schmidt wrote:
>>>
>>> My ssh2dos is very unstable - it usually crashes on exit or after five to
>>> ten minutes.  Do you have this issue as well?  I am curious if I should try
>>> a different version of DOS.
>
>
>
> I made the same experience as Karen: I had SSH2D386 running more or less the
whole morning while logged into the server. I even ran rCRtoprCL for over an
hour to test the program. No crashes, no sudden exits.
>
> Other experiences:
>
> - As I use FreeDOS 1.2 as guest in VirtualBox, I learned that SSH2DOS does
use the hostrCOs CPU by 100 percent. I limit the CPU execution cap in the
VirtualBox settings to 40%, but the fan of my MacBookPro is still running
constantly (but on a lower level than at 100%).
>
> - After logging into the server, I run the command "export LANG=CrCL first.
Otherwise rCRgraphicalrCL console programs like midnight commander or
dpkg-reconfigure will show wrong characters in SSH2DOS.
>
> So far so good. Thanks to you everything is working well now.
>
> Ulrich
>
>
> .
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
<http://sdm.link/slashdot>
> _______________________________________________
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net <mailto:Freedos-user@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/freedos-user
<https://lists.sourceforge.net/lists/listinfo/freedos-user>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! 
> http://sdm.link/slashdot_______________________________________________
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user


--Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
        charset=utf-8

<html><head><meta http-equiv="Content-Type" content="text/html
charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;" class=""><div class=""><br
class=""></div><div class=""><div class=""><blockquote type="cite"
class=""><div class="">Am 13.02.2017 um 06:19 schrieb Dan Schmidt &lt;<a
href="mailto:helpdesk...@gmail.com"; 
class="">helpdesk...@gmail.com</a>&gt;:</div><br 
class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I hope 
I am not committing the dreaded "forum 
necromancyrCL&nbsp;</div></div></blockquote><div class=""><br 
class=""></div><div class="">I had to look that uprCa I really liked the 
picture of the ghoul in the first google result :-))</div><br 
class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" 
class="">but I thought I might document that the 386 version, combined with the 
mentioned "reset" trick, has solved my issues with ssh2dos stability, thank you 
for the idea. &nbsp;</div></div></blockquote><div class=""><br 
class=""></div>Congratulation! But as I see it, it was your idea all 
along.&nbsp;<br class=""><blockquote type="cite" class=""><div class=""><div 
dir="ltr" class=""><div class=""><br class=""></div><div class="">Also, quick 
type-o - "I am not sure why you would want to&nbsp;<i class="">run SSH</i>&nbsp;
in DOS in VirtualBox" &nbsp;I did not mean to imply that running Dos on 
VirtualBox is at all strange.&nbsp;</div></div></div></blockquote><div 
class=""><br class=""></div>WellrCa It kind of IS strange. ;-) The reason is 
simple: I have a bit time to kill at the moment, so I was taking another look 
at my VirtualBox/FreeDOS/Networking images I started a few years ago at&nbsp;<a 
href="https://www.lazybrowndog.net/freedos/virtualbox/"; 
class="">https://www.lazybrowndog.net/freedos/virtualbox/</a>. I updated them 
to FreeDOS 1.2 and was checking if everything still works as expected. And 
well, SSH2DOS wasnrCOt and I was unable to find a fix. So thank you again for 
your help!</div><div class=""><br class=""></div><div class="">At the moment 
IrCOm updating the MS Client pages (sigh).&nbsp;</div></div><div class=""><br 
class=""></div><div class=""><br class=""></div><br class=""><div><blockquote 
type="cite" class=""><div class="">Am 13.02.2017 um 06:19 schrieb Dan Schmidt 
&lt;<a href="mailto:he
lpdesk...@gmail.com" class="">helpdesk...@gmail.com</a>&gt;:</div><br 
class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I hope 
I am not committing the dreaded "forum necromancy" but I thought I might 
document that the 386 version, combined with the mentioned "reset" trick, has 
solved my issues with ssh2dos stability, thank you for the idea. &nbsp;<div 
class=""><br class=""></div><div class="">Also, quick type-o - "I am not sure 
why you would want to <i class="">run SSH</i> in DOS in VirtualBox" &nbsp;I did 
not mean to imply that running Dos on VirtualBox is at all strange. 
&nbsp;</div></div><div class="gmail_extra"><br class=""><div 
class="gmail_quote">On Mon, Jan 30, 2017 at 9:35 PM, Dan Schmidt <span 
dir="ltr" class="">&lt;<a href="mailto:helpdesk...@gmail.com"; target="_blank" 
class="">helpdesk...@gmail.com</a>&gt;</span> wrote:<br class=""><blockquote 
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc 
solid;padding-left:1ex"><div dir="ltr" clas
s="">I didn't try the 386 version, perhaps that will be more stable.&nbsp; 
Also, if you type "reset" before exiting, you can avoid "missing dos screen." 
&nbsp;(IE - the crash every time I exited) &nbsp;<div class=""><br 
class=""></div><div class="">Ulrich, my friend, I am not sure why you would 
want to run DOS in VIrtualBox on a MacBookPro, but I am glad I could help you. 
&nbsp;:-) &nbsp;Years ago, several other technicians laughed at me when I 
bought an old Pentium for $5 saying"You can't do anything with that!" FreeDos 
helped me prove them wrong.</div></div><div class="gmail_extra"><br 
class=""><div class="gmail_quote"><div class=""><div class="h5">On Sat, Jan 28, 
2017 at 8:02 AM, Ulrich Hansen <span dir="ltr" class="">&lt;<a 
href="mailto:my.gr...@mailbox.org"; target="_blank" 
class="">my.gr...@mailbox.org</a>&gt;</span> wrote:<br 
class=""></div></div><blockquote class="gmail_quote" style="margin:0 0 0 
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div 
class="h5"><
div style="word-wrap:break-word" class=""><br class=""><div class=""><span 
class=""><blockquote type="cite" class=""><div class="">Am 28.01.2017 um 06:23 
schrieb Karen Lewellen &lt;<a href="mailto:klewel...@shellworld.net"; 
target="_blank" class="">klewel...@shellworld.net</a>&gt;:</div><div 
class=""><br 
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"
 class=""><span 
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"
 class="">To answer your question for myself, I never have this issue.&nbsp; No 
crashes, and i &nbsp;can spend hours working on line.&nbsp; Further I have done 
more than my share of downloads with sftpd386 a
s well.</span><br 
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"
 class=""></div></blockquote><div class=""><br class=""></div><div class=""><br 
class=""></div></span><blockquote type="cite" class=""><div class=""><span 
class=""><span 
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"
 class="">On Fri, 27 Jan 2017, Dan Schmidt wrote:</span><br 
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"
 class=""></span><span class=""><blockquote type="cite" style="
font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"
 class=""><br class="">My ssh2dos is very unstable - it usually crashes on exit 
or after five to<br class="">ten minutes.&nbsp; Do you have this issue as 
well?&nbsp; I am curious if I should try<br class="">a different version of 
DOS.<br class=""></blockquote></span></div></blockquote></div><div class=""><br 
class=""></div><div class=""><br class=""></div><div class="">I made the same 
experience as Karen: I had SSH2D386 running more or less the whole morning 
while logged into the server. I even ran rCRtoprCL for over an hour to test the 
program. No crashes, no sudden exits.</div><div class=""><br 
class=""></div><div class="">Other experiences:</div><div class=""><br 
class=""></div><div class="">- As I use FreeDOS 1.2 as guest in VirtualBox, I 
learned that SSH2DOS does use the h
ostrCOs CPU by 100 percent. I limit the CPU execution cap in the VirtualBox 
settings to 40%, but the fan of my MacBookPro is still running constantly (but 
on a lower level than at 100%).</div><div class=""><br class=""></div><div 
class="">- After logging into the server, I run the command "export LANG=CrCL 
first. Otherwise rCRgraphicalrCL console programs like midnight commander or 
dpkg-reconfigure will show wrong characters in SSH2DOS.</div><div class=""><br 
class=""></div><div class="">So far so good. Thanks to you everything is 
working well now.</div><div class=""><br class=""></div><div 
class="">Ulrich</div><div class=""><br class=""></div><div class=""><br 
class=""></div><div class="">.</div><div class=""><br class=""></div><div 
class=""><br class=""></div></div><br 
class=""></div></div>------------------------------<wbr 
class="">------------------------------<wbr class="">------------------<span 
class=""><br class="">
Check out the vibrant tech community on one of the world's most<br class="">
engaging tech sites, <a href="http://slashdot.org"; class="">SlashDot.org</a>!
<a href="http://sdm.link/slashdot"; rel="noreferrer" target="_blank"
class="">http://sdm.link/slashdot</a><br
class="">______________________________<wbr class="">_________________<br
class="">
Freedos-user mailing list<br class="">
<a href="mailto:Freedos-user@lists.sourceforge.net"; target="_blank"
class="">Freedos-user@lists.sourceforge<wbr class="">.net</a><br class="">
<a href="https://lists.sourceforge.net/lists/listinfo/freedos-user";
rel="noreferrer" target="_blank" class="">https://lists.sourceforge.net/<wbr
class="">lists/listinfo/freedos-user</a><br class="">
<br class=""></span></blockquote></div><br class=""></div>
</blockquote></div><br class=""></div>
------------------------------------------------------------------------------<br
 class="">Check out the vibrant tech community on one of the world's most<br 
class="">engaging tech sites, <a href="http://slashdot.org"; 
class="">SlashDot.org</a>! <a 
href="http://sdm.link/slashdot_______________________________________________"; 
class="">http://sdm.link/slashdot_______________________________________________</a><br
 class="">Freedos-user mailing list<br class=""><a 
href="mailto:Freedos-user@lists.sourceforge.net"; 
class="">Freedos-user@lists.sourceforge.net</a><br 
class="">https://lists.sourceforge.net/lists/listinfo/freedos-user<br 
class=""></div></blockquote></div><br class=""></body></html>
--Apple-Mail=_629D13CF-1976-4952-BF73-4D5895B4FF36--


--===============0481829807500901100==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===============0481829807500901100==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to