Carl, I made sure that Xy could open quits.pm, then I executed from the CoMmand Line run quits.pm - and it closed but did not re-open. But things never work out of the box on my too-customized XyWrite4. Best, Harry On Mon, Dec 1, 2025 at 3:00 PM Carl Distefano <dmarc-noreply@xxxxxxxxxxxxx> wrote: > Kari, > > I have not encountered this. This is perhaps because I have never > > truly put vDos+ XyWrite through the paces like you do. > > Harry, > > I don't believe I have ever seen that message or experienced that > > crash. > > Thank you both for the feedback. Be glad that you don't see this error, > especially as often as I do, which is VERY often. It's a pain. Admittedly, > I'm at the far end of the bell curve in the way that I use > vDosPlus-XyWrite. I'm constantly leveraging XyWrite/U2 commands by running > Windows executables in the background. vHandles.bat tells me that a single > operation like this can add 8 or 10 open handles to the count. At that > rate, I can hit the 500-handle ceiling pretty quickly, especially when I'm > editing intensely, which is when I can least afford to lose my work. > Fortunately, vHandles.bat solves this problem nicely. > > While I have you here, can I impose on you to try QUITS.PM? > I've updated it today (there were errors). It's part of the vhandles.zip > package (which I've updated), but I'm also attaching the latest version to > this message. If you run QUITS.PM unmodified, it saves all open files and > quits XyWrite. But try editing Save/Get 01, on line 26 of the program, by > inserting the Windows command that you use to start XyWrite. QUITS.PM > should then also restart XyWrite after quitting. The XPL is designed to > work with any version of Xy or NB for DOS, so it's fortuitous that -- if I > recall correctly, you, Harry, run XyWrite 4 while Kari usually runs NB 3 > for DOS. I'm eager to know if QUITS.PM works as advertised for each of > you. I find that it's a handy utility in its own right. > > -- > Carl Distefano > cld@xxxxxxxxxx > > -- _________________