Topic: File Does not close on faster machines (1 of 3), Read 19 times
Conf: Error messages, Crashes
From: Alfred Persson
Date: Friday, July 03, 2009 12:46 AM

Perhaps the clock speed of my new Optiplex 960 causes the search replace to repeat, however the same syntax works fine on my slower machines:

FO('"J:\22\all22.txt" -a "F:\22\20\22.txt"')
Call("fixup20")
FC()

File doesn't close after fixup, a second temp file with a % extension appears:

During the first pass, everything fine, this temp file appears:

01.txt.2044.#02
A0203040506
A0205062930
A0207222939
etc

Then, instead of closing, another temp file opens and its contents seem unrelated to what is in the original file...

01.txt.2044.%02

^z
756544043310
755473336210
354414824210
etc

I've tried doubling the FC(), using the longer syntax, adding line feeds, including File_Quit() to empty the buffer...thinking it would perform the FC() properly, to no avail.

peace
al

 

Topic: File Does not close on faster machines (2 of 3), Read 17 times
Conf: Error messages, Crashes
From: Alfred Persson
Date: Friday, July 03, 2009 09:18 AM

Additional info:

3 gig or less, no problem...4 gig or more, then stated problem occurs on my Optiplex 960...not slower inspiron.

Also, file splitter doesn't work correctly when splitting large files into 4+ gigabytes. Splitter works find 3 gigs or less.

 

Topic: File Does not close on faster machines (3 of 3), Read 16 times
Conf: Error messages, Crashes
From: Pauli Lindgren
Date: Wednesday, December 23, 2009 06:11 AM

On 7/3/2009 9:18:52 AM, Alfred Persson wrote:
> Additional info:
>
> 3 gig or less, no problem...4 gig or
> more, then stated problem occurs on my Optiplex
> 960...not slower inspiron.

> Also, file splitter doesn't work correctly when
> splitting large files into 4+ gigabytes.
> Splitter works find 3 gigs or less.

Alfred, I have no idea about your actual problem, since your question did not contain information about what you are trying to do, which Vedit version you are using etc.

However, I can confirm that splitter.vdm does not work correctly on files larger than 4GB.

I made a test file of size 4.3GB by combining several log files (which are plain text files).
I ran splitter.vdm and choose block size of 999 meg. This should have created 5 segments.
However, it created 6 segments.
Segments .xx1 to.xx4 were 975587kB, .xx5 was 291960kB and .xx6 was 27kB.

The split from .xx5 to .xx6 was done too early, but the data continued correctly. However, .xx6 was truncated.

If you count the sum of the file sizes, the result is exactly 4096 MB.

I used to wonder how the splitter macro on 32bit Vedit could handle files larger than 4GB. Now it seems that it can't. So, it is only useful for files in range 2GB to 4GB. This should be mentioned in the documentation.

--
Pauli