Subj : Pimpwars keeps deleting my DOOR.SYS file?
To   : Terry Rankin
From : Gryphon
Date : Tue Jan 09 2018 09:29 am

On 01/06/18, Terry Rankin said the following...
 
 TR> On Saturday, January 6, 2018 at 5:23:52 PM UTC-5, g00r00 wrote:
 TR> > TR> Yes, the D3 DOOR32 menu option is a confusing name because this opti
 TR> >  TR> actual creates several "door type" files. It creates all of the
 TR> >  TR> following each time its executed: CHAIN.TXT door32.SYS DOOR.SYS
 TR> >  TR> DORINFO1.DEF
 TR> >
 TR> > In Linux D3 is the same as DD except that it also creates door32.sys.  T
 TR> is
 TR> > more of a difference between the two on other platforms, but in Linux yo
 TR> > should be fine using either one for a DOOR.SYS door.
 TR> >
 TR> > I am not sure that PimpWars itself is deleting the file as Mystic does d
 TR> > all of the drop files upon returning to the BBS, so that might be what
 TR> > happens with the drop file.  Or not, but I thought I'd mention it! :)
 TR> >
 TR> >  TR> I have a bad feeling it might just be some oddness with "qemu". Its
 TR> >  TR> throwing some crazy errors like: get_cluster_count_for_directory:
 TR> >  TR> Assertion `mapping->mode & MODE_DELETED' failed. Aborted
 TR> >
 TR> > This was my thoughts too considering you have other doors working and ar
 TR> > savvy enough to have done that.  I have no experience with QEMU on the P
 TR> > doors so I am not very useful here.
 TR> >
 TR> > As a possible alternative:
 TR> >
 TR> > I think there are still some 3rd party door servers that you can use a R
 TR> > gate from your Mystic BBS to connect with.  Basically you'd create an ac
 TR> > with their service, they give you a login and password, and then you set
 TR> > outbound RLOGIN or SSH command to kick off the doors running on their
 TR> servers.
 TR> >
 TR> > Maybe Gryphon will see this (he wrote that guide) and have some addition
 TR> > input...
 TR> 
 TR> I FIGURED IT OUT! :)
 TR> 
 TR> DOS is case sensitive....well sort of. ;)
 TR> 
 TR> I got rid of all of my @ECHO OFF commands to see what the heck was going
 TR> on.
 TR> 
 TR> I thought DOS isn't case sensitive therefore it doesn't matter if I have:
 TR> D:\DOORS\bnu\bnu
 TR> OR
 TR> D:\DOORS\BNU\BNU
 TR> 
 TR> Turns out that the lower case version resolved to this:
 TR> D:\DOORnnu
 TR> 
 TR> What the heck! :)
 TR> 
 TR> and got a Bad command or filename - "D:\DOORS".
 TR> 
 TR> I guess \b is a option or switch or has some meaning.
 TR> 
 TR> Ok. Long story short...
 TR> Changed it to D:\DOORS\BNU\BNU
 TR> 
 TR> and the output goes from:
 TR> D:\DOORnnu
 TR> Bad command or filename - "D:\DOORS".
 TR> 
 TR> TO:
 TR> D:\DOORS\BNU\BNU
 TR> 
 TR> BNU Revision 5 FOSSIL Compatible Communications Driver Ver 1.70
 TR> Copyright (C) 1989 by David Nugent & Unique Computing Ptd Ltd
 TR> 1 Port(s) available  0 Port(s) active
 TR> 
 TR> BNU: Communications driver now resident
 TR> ...
 TR> AND the GAME STARTS!!!!
 TR> 
 TR> WHEW! Changing that bnu to BNU took me an entire day to figure
 TR> out.HAHAHA! What the heck. :)

As I recall, with DOS, you have to do the double backslash when scripting DOS
paths.

So 
D:\DOORS\BNU\BNU
shold be scripted as
D:\\DOORS\\BNU\\BNU\\

I just checked my script that you referenced, and I can see that I did script
it with the double backslash with all my DOS paths.

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
 * Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (1:106/324)

.