Forum: EasyBoot
Topic: insufficient memory errors after booting IMG
started by: rtfm
Posted by rtfm on Nov. 04 2004,15:06
Anyone messed around with < NTFSPRO > and EB?

EB loads the IMG file (98 os files), NTFSPRO loads and assigns the drive letters.  My batch file then tries to execute NTFSCHK and I get an error "insufficient memory".  This works fine if I do all this outside launching it from EB, but I seem to run out of memory with EB.

All I'm trying to accomplish is to be able to run some type of chkdsk utility on NTFS partitions to clear up any issues w/o the intervention of booting to a 2K or XP install cd and doing the repair console.

Another issue I'm having is creating a IMG file for a dos based virus scan.  Since most HD's are NTFS, I need to again load NTFS support.  That part goes fine.  The batch then calls mcafee, but instead of scanning it just waits a second and then kicks back to the dos prompt.  Again, this works fine outside of EB.  So I'm thinking it's a memory issue, though I could be wrong.

So anyone have any advice for these issues?  Or perhaps alternatives for chkdsk and virus scan on NTFS volumes w/o much intervention.

Thanks again for any help!
Posted by Gork on Nov. 04 2004,15:15
I can't help you with your problem.  Perhaps you've already heard of BartPE Builder?  If not, check it out.  It lets you create a customized WinPE CD you can boot to, and I use such a CD for what you are describing...
Posted by rtfm on Nov. 04 2004,15:34
Got it worked out last night.  When NTFSPRO loaded into memory it consumed all the extended memory, preventing anything from running after that.  Found out there's a way to call NTFSPRO and a dos application within it's command line then unloads itself right after.  You also need to make sure you're using the DOS4GW version of NTFSPRO files otherwise programs like McAfee dos scan won't run.

For McAfee virus scan I had to change the line to this.

ntfspro "/sa:\mcafee\scan.exe /clean /all d:"

This will load NTFSPRO call mcafee to scan the new mounted ntfs volume (d: in this example) then unload after it's done.

For ChkDsk I realized I don't fully read documentation late at night.  I thought I needed to load NTFSPRO first THEN call NTFSCHK, that isn't the case.  To have ChkDsk check all ntfs volumes you simply run NTFSCHK with the following.

ntfschk /f *

* will mount any volume found and assign a drive letter.

Now it all works like a charm.