Home > Archive > Cobol > August 2007 > Powercobol slow on Intel Core duo
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Powercobol slow on Intel Core duo
|
|
| Massimo 2007-08-21, 7:55 am |
| Hi ,
I have replace my old PC with one new based on Intel Core duo 1800 MHz.
Using the Powercobol is especially very slow in the function of Load/Save
project.
On my portable PC with processor AMD 3000 the same application with same
project go almost to a triple speed. : (.
Exist a solution?
The best regards.
Massimo.
| |
| Pete Dashwood 2007-08-21, 6:55 pm |
|
"Massimo" <blue_max_53@hotmail.com> wrote in message
news:OFyyi.92213$%k.235571@twister2.libero.it...
> Hi ,
> I have replace my old PC with one new based on Intel Core duo 1800 MHz.
> Using the Powercobol is especially very slow in the function of Load/Save
> project.
> On my portable PC with processor AMD 3000 the same application with same
> project go almost to a triple speed. : (.
> Exist a solution?
> The best regards.
> Massimo.
>
>
I'm running PowerCOBOL on a core 2 Duo and it flies...
Look for something like large bitmaps included in your project, or possibly,
project directories that are distributed all over.
Put all files for the project into ONE directory, then try removing them one
at a time until you find what is causing the problem.
Also, with regard to your other request about Faxing from PowerCOBOL:
1. Get a third party FAX COM component, install it and make sure it has
registered as a COM server component. You can then drop it from your
PowerCOBOL toolbar into your project just as you would any other control,
and manipulate its methods and properties. (Easy, future proof, but may
cost)
2. Shell out and execute the FAX software already on your computer through
the Windows API. "Execute" (no cost, but messy and not future proof)
3. Set a link to a standard Web-based FAX portal. (May require a
subscription and requires internet connection, but FAX requires a phone
connection anyway...)
4. (This is what I would do...) If you install the XP Fax service on your
system (Add/Remove Programs > Windows components > Fax Service) you can use
the COM component that is already in your OS (Win XP). It has a ProgID of
"FaxService.FaxService.1" You can instantiate it into a PowerCOBOL or
NetCOBOL program using:
Repository.
COM AS "*COM". (This should already be there in a PowerCOBOL
program...)
working-storage section.
01 fax-progID pic x (25) value "FaxService.FaxService.1" .
01 objFAX usage is OBJECT REFERENCE COM.
....
procedure division.
....
invoke COM "CREATE-OBJECT" using fax-progID
returning objFAX
end-invoke
....
Use an Object Browser to find out what Methods and Properties it has. (If
you have MS Office installed, Word has an Object Browser in it. Open a blank
document then TOOLS>Macro>Visual Basic Editor. Once you have opened VB,
TOOLS>References and tick the box for "faxcom 1.0 Type Library" and possibly
"MicroSoft Fax Service Extended COM Type Library" You will find you can do
anything with Fax that you could ever want to do, including setting up cover
pages, routing incoming to folders, etc. etc.)
If you add an object reference in the PowerCOBOL Form View and bring up the
Browse Dialogue, you could browse to C:\WINDOWS\system32\fxscom.dll
This should add the fax server to your toolbox, and then the methods and
properties are readily available
(I haven't tried it because I don't have COBOL on the machine where I'm
writing this, but it should work.)
I had a quick look at it in the VBA Object Browser in Word, and it looks
like:
*> get a reference to a fax document
invoke objFax "FaxDoc"
returning objFaxDoc
end-invoke
*> set a cover page and send it...
invoke objFaxDoc "set-CoverpageNote"
using fax-coverpage-text
end-invoke
invoke objFaxDoc "SendCoverPage" end-invoke
.... might be something along the lines of what you need. You might have to
connect to a device or server first. Experiment with the Methods and
properties until it works.
If you don't have the time or inclination for it, use one of the other
options above.
Good luck!
Pete.
--
"I used to write COBOL...now I can do anything."
| |
| Richard 2007-08-21, 6:55 pm |
| On Aug 21, 9:57 pm, "Massimo" <blue_max...@hotmail.com> wrote:
> Hi ,
> I have replace my old PC with one new based on Intel Core duo 1800 MHz.
> Using the Powercobol is especially very slow in the function of Load/Save
> project.
Let us look for clues here. PowerCobol is a Windows thing. "New one"
implies that it is Windows Vista.
> On my portable PC with processor AMD 3000 the same application with same
> project go almost to a triple speed. : (.
"Portable PC" is not specified as 'new'. Perhaps that is XP.
> Exist a solution?
Don't use Vista.
Vista is broken in many ways. Playing music may kill network speed,
disk transfers may be appallingly slow, UI is annoying.
| |
| Pete Dashwood 2007-08-22, 3:55 am |
|
--
"I used to write COBOL...now I can do anything."
"Pete Dashwood" <dashwood@removethis.enternet.co.nz> wrote in message
news:5j0flnF3rdarrU1@mid.individual.net...
>
>
> "Massimo" <blue_max_53@hotmail.com> wrote in message
> news:OFyyi.92213$%k.235571@twister2.libero.it...
> I'm running PowerCOBOL on a core 2 Duo and it flies...
>
> Look for something like large bitmaps included in your project, or
> possibly, project directories that are distributed all over.
>
> Put all files for the project into ONE directory, then try removing them
> one at a time until you find what is causing the problem.
>
> Also, with regard to your other request about Faxing from PowerCOBOL:
>
> 1. Get a third party FAX COM component, install it and make sure it has
> registered as a COM server component. You can then drop it from your
> PowerCOBOL toolbar into your project just as you would any other control,
> and manipulate its methods and properties. (Easy, future proof, but may
> cost)
>
> 2. Shell out and execute the FAX software already on your computer through
> the Windows API. "Execute" (no cost, but messy and not future proof)
>
> 3. Set a link to a standard Web-based FAX portal. (May require a
> subscription and requires internet connection, but FAX requires a phone
> connection anyway...)
>
> 4. (This is what I would do...) If you install the XP Fax service on your
> system (Add/Remove Programs > Windows components > Fax Service) you can
> use the COM component that is already in your OS (Win XP). It has a ProgID
> of "FaxService.FaxService.1" You can instantiate it into a PowerCOBOL or
> NetCOBOL program using:
>
> Repository.
> COM AS "*COM". (This should already be there in a PowerCOBOL
> program...)
>
> working-storage section.
> 01 fax-progID pic x (25) value "FaxService.FaxService.1" .
> 01 objFAX usage is OBJECT REFERENCE COM.
> ...
> procedure division.
> ...
> invoke COM "CREATE-OBJECT" using fax-progID
> returning objFAX
> end-invoke
> ...
> Use an Object Browser to find out what Methods and Properties it has. (If
> you have MS Office installed, Word has an Object Browser in it. Open a
> blank document then TOOLS>Macro>Visual Basic Editor. Once you have opened
> VB, TOOLS>References and tick the box for "faxcom 1.0 Type Library" and
> possibly "MicroSoft Fax Service Extended COM Type Library" You will find
> you can do anything with Fax that you could ever want to do, including
> setting up cover pages, routing incoming to folders, etc. etc.)
>
> If you add an object reference in the PowerCOBOL Form View and bring up
> the Browse Dialogue, you could browse to C:\WINDOWS\system32\fxscom.dll
>
> This should add the fax server to your toolbox, and then the methods and
> properties are readily available
>
> (I haven't tried it because I don't have COBOL on the machine where I'm
> writing this, but it should work.)
>
> I had a quick look at it in the VBA Object Browser in Word, and it looks
> like:
>
> *> get a reference to a fax document
>
> invoke objFax "FaxDoc"
> returning objFaxDoc
> end-invoke
> *> set a cover page and send it...
>
> invoke objFaxDoc "set-CoverpageNote"
> using fax-coverpage-text
> end-invoke
>
> invoke objFaxDoc "SendCoverPage" end-invoke
>
> ... might be something along the lines of what you need. You might have to
> connect to a device or server first. Experiment with the Methods and
> properties until it works.
>
> If you don't have the time or inclination for it, use one of the other
> options above.
>
> Good luck!
>
> Pete.
> --
> "I used to write COBOL...now I can do anything."
>
| |
| Pete Dashwood 2007-08-22, 3:55 am |
|
Massimo,
I have updated this response under the original thread on how to send a Fax
from PowerCOBOL.
What is here is on the right track but there were a few things that were
wrong.
Pete
--
"I used to write COBOL...now I can do anything."
TOP POST - Nothing new below.
"Pete Dashwood" <dashwood@removethis.enternet.co.nz> wrote in message
news:5j0flnF3rdarrU1@mid.individual.net...
>
>
> "Massimo" <blue_max_53@hotmail.com> wrote in message
> news:OFyyi.92213$%k.235571@twister2.libero.it...
> I'm running PowerCOBOL on a core 2 Duo and it flies...
>
> Look for something like large bitmaps included in your project, or
> possibly, project directories that are distributed all over.
>
> Put all files for the project into ONE directory, then try removing them
> one at a time until you find what is causing the problem.
>
> Also, with regard to your other request about Faxing from PowerCOBOL:
>
> 1. Get a third party FAX COM component, install it and make sure it has
> registered as a COM server component. You can then drop it from your
> PowerCOBOL toolbar into your project just as you would any other control,
> and manipulate its methods and properties. (Easy, future proof, but may
> cost)
>
> 2. Shell out and execute the FAX software already on your computer through
> the Windows API. "Execute" (no cost, but messy and not future proof)
>
> 3. Set a link to a standard Web-based FAX portal. (May require a
> subscription and requires internet connection, but FAX requires a phone
> connection anyway...)
>
> 4. (This is what I would do...) If you install the XP Fax service on your
> system (Add/Remove Programs > Windows components > Fax Service) you can
> use the COM component that is already in your OS (Win XP). It has a ProgID
> of "FaxService.FaxService.1" You can instantiate it into a PowerCOBOL or
> NetCOBOL program using:
>
> Repository.
> COM AS "*COM". (This should already be there in a PowerCOBOL
> program...)
>
> working-storage section.
> 01 fax-progID pic x (25) value "FaxService.FaxService.1" .
> 01 objFAX usage is OBJECT REFERENCE COM.
> ...
> procedure division.
> ...
> invoke COM "CREATE-OBJECT" using fax-progID
> returning objFAX
> end-invoke
> ...
> Use an Object Browser to find out what Methods and Properties it has. (If
> you have MS Office installed, Word has an Object Browser in it. Open a
> blank document then TOOLS>Macro>Visual Basic Editor. Once you have opened
> VB, TOOLS>References and tick the box for "faxcom 1.0 Type Library" and
> possibly "MicroSoft Fax Service Extended COM Type Library" You will find
> you can do anything with Fax that you could ever want to do, including
> setting up cover pages, routing incoming to folders, etc. etc.)
>
> If you add an object reference in the PowerCOBOL Form View and bring up
> the Browse Dialogue, you could browse to C:\WINDOWS\system32\fxscom.dll
>
> This should add the fax server to your toolbox, and then the methods and
> properties are readily available
>
> (I haven't tried it because I don't have COBOL on the machine where I'm
> writing this, but it should work.)
>
> I had a quick look at it in the VBA Object Browser in Word, and it looks
> like:
>
> *> get a reference to a fax document
>
> invoke objFax "FaxDoc"
> returning objFaxDoc
> end-invoke
> *> set a cover page and send it...
>
> invoke objFaxDoc "set-CoverpageNote"
> using fax-coverpage-text
> end-invoke
>
> invoke objFaxDoc "SendCoverPage" end-invoke
>
> ... might be something along the lines of what you need. You might have to
> connect to a device or server first. Experiment with the Methods and
> properties until it works.
>
> If you don't have the time or inclination for it, use one of the other
> options above.
>
> Good luck!
>
> Pete.
> --
> "I used to write COBOL...now I can do anything."
>
| |
|
|
|
|
|