home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   JAMNNTPD      Support for the JAMNNTPD software client      2,630 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,828 of 2,630   
   Paul Quinn to Nicholas Boel   
   smapinntpd   
   25 Nov 18 10:05:39   
   
   Hi! Nick,   
      
   On 11/24/2018 11:44 PM, you wrote:   
      
    NB> So with this being said, are you referring to Win98se's display *before*   
    NB> VBox is even involved? If so, then it's probably not an issue with VBox   
    NB> itself. Otherwise, If it only happens in VBox, you can probably try to   
    NB> use the built in default drivers in VBox settings.   
      
   Firstly, there is /nil/ support in vBox for anything Win9x.  T'ain't no "Guest   
   Additions" and no working OOTB Windows SVGA driver, so, the SVGA driver had   
   been written by a third party to fill the gap.  The vBox people say it is all   
   exceedingly very bloody difficult and don't even recommend installing Win9x in   
   vBox.  Hence, no support.   
      
   OTOH, wouldn't you want to use a multi-tasking GUI OS that only uses 128Mb RAM   
   (maybe just 64Mb but I didn't want to be overly stingy)? Especially if such   
   can give renewed life to 20+ years-old accumulated utilities & custom   
   scripts.  :)   
      
    PQ>> runs great, but I found through early experimentation that it neither   
    PQ>> will run DOS programs in a window nor full-screen.   
      
    NB> VBox or Win98se?   
      
   The alternate (vBox) SVGA driver-supported system.  (Entirely different   
   driver, BTW.)  It's been running happily as a Win98se system for quite a few   
   years, so long as I throw Windows *only* apps at it.  Any attempted   
   windowed/full-screen DOS sessions lock it up.  It still runs so long as I'm   
   careful.   
      
   It was even running Radius from a LAN share on it as well as its primary job   
   for a couple of weeks recently, but I've stopped doing that after Radius   
   TRAP-ped unexpectedly one morning.  That was for a downlink who can/will-not   
   change his iRex _from_ port 24554.   
      
    NB> I thought the whole point of this was *not* to use a "swiss army knife"   
    NB> BBS software? I mean whatever works for you of course, and I know you've   
    NB> used Mystic for quite some time, so obviously the comfort level is there   
    NB> for you.   
      
   There's another 32-bit Linux tosser?  Where?  What?  Hunh?  Pray tell, as I   
   have not heard of one other than HPT.   
      
   Mystic fitted nicely into my hardware & software constraints.  I am very   
   pleased with it.  I haven't been this happy for nearly a decade.  Can't you   
   tell from my smile?  :)   
      
    NB> All the software is there, you just have to write batch files or scripts   
    NB> to use them in a way that works for you obviously. Not sure how much DOS   
    NB> voodoo you would need, as I thought all, or most of your VMs were Linux   
    NB> based?   
      
   Yes.  The DOS doin's was just after fire was tamed and the wheel introduced   
   into general use.  Think of a time when Husky's nodelist handling stuff first   
   became available.   
      
   I don't do DOS any more.  Just simple procedural bash-ing.   
      
   Cheers,   
   Paul.   
      
   --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0   
    * Origin: I logon, therefore I am. (3:640/1384.125)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca