We ran out of time on this, and the oakcdrom.sys worked for us (and had a
good track record of working), Our memory was being used by NTFSDOS, which
we needed to use, and can't be unloaded, I'm guessing where that's the
missing chunk has gone.
RDisk worked very well and allowed us to specify a sp
Hi Mark,
strange that you only 470k free...
> Problem is, now the ghost process is crashing with a read error from the
> DVD, which I know don't contain any errors. Could this be related to me
> using UIDE.SYS rather than our previous driver (oakcdrom.sys)?
Oakcdrom sounds very outdated and m
* NOEMS (disables EMS almost 100%, and its pageframe entirely)
* I=B000-B7FF (use Monochrome area, might work, or not)
* I=TEST (test for additional UMBs)
* X=TEST (test for additional UMBs)
Thanks, done this and it's freed up some more mem with no adverse side
effects so far.
It's a possibilit
We do need lots of drive letters for what we are doing (need to read the
contents of ntfs partitions using ntfsdos readonly driver), and there may
be variable amounts of them, do ramdrive is on y: and cdrom on z:
Will try the other tweaks to jemmex once I got the cd reading issue sorted.
On Mar 8
Hi,
On Thu, Mar 8, 2012 at 8:05 AM, Mark Gillespie wrote:
>
> One last question, all these memory managers and such, is there a
> recommended set for a modern PC?
>
> At the moment, my fdconfig.sys looks like:
>
> DEVICE=A:\JEMMEX.EXE
> SHELL=A:\COMMAND.COM A:\ /E:512 /P
> DOS=HIGH,UMB
> DOSDATA=
Mark,
> Thanks, after using all the excellent advice so far, I am **ALMOST** back
> up and running, the environment variable problem has been worked around,
> and I have taken onboard the memory saving advice (have about 470k of
> conventional memory, which should be ample, how much did billyboy
i have a small update on my original email (i haven't had a chance to try
the items below).
When I run Ghost, the CD drive is listed twice, once via it's drive letter
and once via it's ATAPI direct access.
Access via drive letter fails repeatably.
Access directly works.
I don't know if that shed
Op 8-3-2012 18:43, Mark Gillespie schreef:
> Thanks, after using all the excellent advice so far, I am **ALMOST**
> back up and running, the environment variable problem has been worked
> around, and I have taken onboard the memory saving advice (have about
> 470k of conventional memory, which shou
Thanks, after using all the excellent advice so far, I am **ALMOST** back
up and running, the environment variable problem has been worked around,
and I have taken onboard the memory saving advice (have about 470k of
conventional memory, which should be ample, how much did billyboy say we
wouln't n
Mark,
> Yep, just tried Rdisk and it works as expected (when loaded from
> Autoexec.bat), I can assign a known drive letter and then not have
> to "faff around" trying to locate the ramdisk using findtdsk.exe.
>
> I don't think rdisk was around in 2003 when we set up our stuff
> originally, which
Yep, just tried Rdisk and it works as expected (when loaded from
Autoexec.bat), I can assign a known drive letter and then not have to "faff
around" trying to locate the ramdisk using findtdsk.exe.
I don't think rdisk was around in 2003 when we set up our stuff originally,
which I why we went tdsk
for what it's worth,
RDISK with the size parameter /Snn (nn being the number of megabytes)
is, in real terms, more stable than the ram disk you're using,
which i've *never* gotten working right because it always messes up for me.
rdisk on the other hand has *always* worked for me,
it gives you 2
... And FreeCom version 0.83 beta 26 doesn't work... So it's something
that was introduced way back when. Any way of finding the changelog
between these versions?
On 8 March 2012 09:59, Mark Gillespie wrote:
>
> Hmm, interestingly, I just replaced our FreeCom with the old version we
> were u
Hmm, interestingly, I just replaced our FreeCom with the old version we
were using, and everything works again, meaning it's almost certainly
something FreeCom related.
The version that works:
FreeCom version 0.82 pl 3 XMS_Swap [Dec 10 2003 06:49:32]
--
On 8 March 2012 01:21, Rugxulo wrote:
> Hi,
> Is this all the DOS Watcom application does? Just ask for some basic
> info to pass back to the caller (to run as parameters to the ghosting
> app)?
>
>
Yes, this is all it does.
> > We had a clumsy turbodisk memory partition (there is no writable
Hi,
On Wed, Mar 7, 2012 at 5:57 PM, Mark Gillespie wrote:
>
> What we have, is a FreeDOS bootCD for "ghost" imaging hardware, and we have
> a DOS application (written in Watcom) that prompts the user for some
> information. Now the problem was when we wrote this, that there was no way
> to store
> Now the problem was when we wrote this, that there was no way
> to store any data to pass it back to the calling batch file.
>
> We had a clumsy turbodisk memory partition (there is no writable storage
> on
> our system when running under FreeDOS), so we write a batch file in that
> partition w
We have been using FreeDOS on a project for many years, it's an old
release, but it did the trick as they say.
However we have been forced to update due to some other weirdness, and as a
result, it's broken a particular bit of functionality that our batch
scripts rely on. I hoping there is an eas
18 matches
Mail list logo