Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


381 posts

Ultimate Geek
+1 received by user: 13

Subscriber

Topic # 56612 18-Jan-2010 22:36
Send private message

Anyone familiar with TextPad?

I have used this for many years and generally find it very stable - no problems opening ASCII text docs up to 1GB plus.

However I have just had to generate a 3GB file (8m+ records) and was surprised to get a "disk full" message when I attempted to open it in TextPad.

System is Vista64 SP2 Bussiness, 4GB RAM, 6.5GB spare on c: drive, and several hundred GB spare on the drive that the file is located on.

I know that TP creates a temp file on c:drive when it opens a file, but I thought 6.5GB would have been sufficient for that?

Is this:

   1. a TP limit (32bit application)?  
   2.  a Disk resource limit? 
   3.  Or is it the really insufficient RAM being reported as "disk full"?

I created a shortened version of the file (~3m records, 1.4GB).  That opens in TP without problem

Any help much appreciated.



 

Create new topic
4013 posts

Uber Geek
+1 received by user: 524

Trusted

  Reply # 291064 19-Jan-2010 08:33
Send private message

Could be file system, you running NTFS? should be just check if not FAT32 has a 2gb file limit.

Could also be that text pad has a 2gb file limit. I've used vedit in the past and ultraedit, but not tried opening/saving a 3gb file, 1 and a half would have been my limit for a large postscript file.




Previously known as psycik

NextPVR: 
Gigabyte AMD A8 Brix --> Samsung LA46A650D via HDMI, NextPVR,
OpenHAB: ODroid C2 eMMC DriveOpenHAB with Aeotech ZWave Controller, Raspberry PI, Wemos D1 Mini, Zwave and Bluetooth LE Sensors
Media:Chromecast v2, ATV4, Roku3, HDHomeRun Dual
Windows 2012 
Host (Plex Server/Crashplan): 2x2TB, 2x3TB, 1x4TB using DriveBender, Samsung 850 evo 512 GB SSD, Hyper-V Server with 1xW10, 1xW2k8, 2xUbuntu 16.04 LTS, Crashplan, NextPVR channel for Plex,NextPVR Metadata Agent and Scanner for Plex




381 posts

Ultimate Geek
+1 received by user: 13

Subscriber

  Reply # 291100 19-Jan-2010 09:28
Send private message

64bit OS. Both drives NTFS.

Go Hawks!
877 posts

Ultimate Geek
+1 received by user: 49

Trusted
Subscriber

  Reply # 291112 19-Jan-2010 09:56
Send private message

Had a quick look at: http://www.textpad.com/products/textpad/specifications.html

It has the following passage:

It can handle file sizes up to the largest contiguous chunk of 32-bit virtual memory.


I imagine that exact file limit is going to depend on exactly how your 32-bit virtual memory is laid out for TextPad, I vaguely recall that a popular method of dealing with 32 bit memory and more than 4GB was to have a flat model for the first 3GB, and paging for the last 1Gb (Of physical RAM).

Given that it's the 32Bit version of TextPad on a 64bit OS with 4GB of RAM, I suspect that the error messages are because of TextPad limitations, and the message about Disk Full is most likely due to TextPad "identifying" that as the problem.



381 posts

Ultimate Geek
+1 received by user: 13

Subscriber

  Reply # 291182 19-Jan-2010 14:07
Send private message

Thanks for the follow up. I suspected it most likely the case.

Create new topic

Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.