FiveTech Software tech support forums

Guys:

I tried to use the Borland Resource Workshop Ver. 4.5 and I'm getting the following message:
The Win16 Subsystem has insufficient resources to continue running. Clink on OK, close your applications, and restart your machine.

I rebooted and reinstalled and got the same results. Windows XP SP3 8GB RAM (3.25GB visible), Core 2 Quad Q9550 2.83GHz.

Any ideas or where I can download the latest version ? Thank you in advance.

i am affraid it has nothing to do with borland's version

the resource you are editing "rc" or dll has reeached a limit, BR can not handle it

you have to split it into 2 resources

Hth

Richard

My advice is exactly the same as Richard's.

In my main application, I have split up my resources into 8 rc-files or 8 res-files. No problem at all.

Good luck.

Not convinced its a limit problem. If your using resource workshop and u have dos open it may be using up the 16 bit subsystem. Go to task manager click on process and see how many times your using ntvdm.exe. It is the subsystem. If your running to many 16bit programs that could be the problem.

Hunter..

Why don't you move towards PELLES C IDE, all your problems will go away.

I have a HUGE RC and I work with it with no problems at all

http://www.smorgasbordet.com/pellesc/

Give it a try.

From Chile
Adolfo

Guys:

Thank you for all your responses. In the case I explained, I have not loaded any RC yet. The Workshop just simply does not boot. Yesterday (Friday) I turned off the computer and went I came back, launched the Workshop and it worked. Antivirus and anti-spyware are ok. I think it's just one of those occasions where strange things happens under Windows. Again, thank you all.

Hunter,

Yes, memory leaks happen all the time, so rebooting is always something to check.

Also, Workshop uses some DLLs and sometimes another app loads an older version of the same DLL that Workshop uses. Then when you try to run Workshop it sees the older DLL is already loaded so it try to use it and strange things happen. Again rebooting will fix this.

Regards,
James

James:

Thank you.


Gustavo