I just got a call from someone who had a Native D3 installation, but
will not receive a login prompt from D3, instead receiving the dreaded
Not Enough Disk Space (Abort/Reserve/Quit) -



No matter what choice they make, no logon prompt.



Their issue erupted due to running thousands of reports in error, and
turning the printer off, then someone burning through the reserve. Of
course, THEN they call.



Is there a way in the 'boot' process that I can force it to shed the
print jobs or some file(s) they can 'live without' to get more space?
Or is the only answer increasing the actual size of the Pick Partitions?
Of course, the last backup they have is pre-historic - anyone remember
what version of D3 allowed the increase in Partition size without
without requiring a full restore?



Been a while since I did 'Native' D3 work - most everyone I work with is
D3/Linux. Any ideas would be appreciated...


--
Posted via http://dbforums.com

dwolverton wrote:

Is this D3 Linux or D3-ProPlus? Linux has a *pick0* file you
could potentially expand with new disk statements. There is no
D3 Native that I know of.

Patrick, <;=?

P.S. How old is your last file-save.


--
"Wrong is wrong, even if everyone is doing it.
Right is right, even if no one is doing it." ~ St. Augustine

I assume that "Native D3" means PRO/Plus ?

You MIGHT be able to break out of the coldstart EARLY IN THE GAME and
enter a ":" at the ! prompt ? If you are lucky, then SP-EDIT MUD, OR
try DELETE DICT BP HOT-BACKUP.SLAVE (you can always re-compile) & then
SP-EDIT MUD ?

The fear (expectation) is that this will not work :-(, in which case
I'd contact RD support ---> their IS a way to manipulate overflow from
the system debugger, but I don't have details

BON CHANCE !!


dwolverton <member43948 (AT) dbforums (DOT) com> wrote

I am sure i had this problem on d3/nt and if my memory serves me correctly ,
i made a copy of the pick0 blob file and then copied in a copy from another
directory within the d3 sub-directory. I hope that isnt as clear as mud and
it helps.

I am sure once you do this and get it up and running you close pick down and
re-copy the original pick0 blob back to where it came.


Cheers

Shane




"dwolverton" <member43948 (AT) dbforums (DOT) com> wrote