Hi again DG
Looks great 42000 samples - drooolll

What does your "my computer->properties" report of available memory
on startup?

What do you mean by 'hack' - is this a real program hack or just a switch you set somewhere?

thx

You're setting a switch on the hosts' .exe file so that the OS believes the executable is "LargeMemoryAware". This causes the loader to behave differently and allowing for a larger memory allocation. You need to run a utility (comes with some development packages) to apply the switch and that's what could be called a "hack". The problem is if the host application wasn't really written to be LMA it could lead to hard crashes.

If these tests are positive however, we could possibly bug the host developers to set the switch officially and thus support the 3GB switch. I've discussed this already with one developer and they had tested this before but with mixed results as they managed to get the system onto its knees during hard stress tests... Ups and downs.

/Mattias

@Another User said:

What do you mean by 'hack' - is this a real program hack or just a switch you set somewhere?

thx

Mattias' answer explains this better than I could. I call it a hack because you have to get your hands "dirty" opening Command Prompt etc. It's not exactly elegant.

DG

@DG said:

Mattias' answer explains this better than I could.

For the record..what the humble Daryl tries to say here is: "Mattias explains this better in English than I could do in Swedish" [:D]

/Mattias

@DG said:

Mattias' answer explains this better than I could.

For the record..what the humble Daryl tries to say here is: "Mattias explains this better in English than I could do in Swedish" [:D]

/Mattias
[:O]ops:

DG

Dear Daryl and Matthias,

Could you tell us the name of the utility?

Kind Regards,

Nick.

@nicks@aubergine.co.uk said:

Dear Daryl and Matthias,

Could you tell us the name of the utility?

Kind Regards,

Nick.

I have sent a detailed report to Paul and he is currently testing it. I would rather not post the method I used until VSL has looked at it in detail, as it could cause your system to become horribly unstable. However, if you really, really, really want to know, PM me.

DG

OK, just a small update to say that in spite of trying my hardest I can only get FXT to crash when I load more than 2.85Gb samples and it seems to be stable even with the memory this full.

I am about to test Gigastudio and VI on the same machine and later will try K2 and VI, just to see if they like to play. I already know that GS and K2 are not really fond of each other [:'(]

I will update the tests to include 3Gb memory when I have time to take the top off the PC and mess around again...!

DG

Hey DG for us 'low-tech hacks' - could you tell me how to get my 4 slaves set up for this 3 gig switch. What is it exactly (soft or hardware). The .exe you mentioned.

My 4 machines all have 2 gig ram but range in age form 2 months to 2 years old (2.7 to 3.2 ghz).

Thanks for any help you can be on this.


Rob

Looks very promising - still awaiting the 3GB machine test. Anyway this looks like a releatively cheap way of getting more milage out of each computer.

@Rob Elliott said:

Hey DG for us 'low-tech hacks' - could you tell me how to get my 4 slaves set up for this 3 gig switch. What is it exactly (soft or hardware). The .exe you mentioned.

My 4 machines all have 2 gig ram but range in age form 2 months to 2 years old (2.7 to 3.2 ghz).

Thanks for any help you can be on this.


Rob

It is all software based.

The switch is an alteration to the boot.ini file in order that Windows allows you to use up to 3GB for applications and 1GB for Windows as opposed to 2GB each. Even with only 2GB RAM there can be an advantage in using the switch (for me it was around 200MB of samples), but it can make the system unstable. I have sent all details to VSL and they are testing at the moment.

In the meantime, let me know what host you are intending to use on your VI machines.

DG

I added a small comment on the issue in the VI and memory configuration thread as well... [[;)]]

/Mattias

@Mattias Henningson said:

I added a small comment on the issue in the VI and memory configuration thread as well... [[;)]]

/Mattias

I was hoping you would, to save my typing fingers [:)]

DG

Daryl, do what you do best and get on with that link I forwarded instead... [[;)]]

/Mattias

@Mattias Henningson said:

Daryl, do what you do best and get on with that link I forwarded instead... [[;)]]

/Mattias

I'm on the case already..................!

DG

Haha, I knew it! You have way too much spare time... [:D]

/Mattias

@Mattias Henningson said:

Haha, I knew it! You have way too much spare time... [:D]

/Mattias

No, I just avoid work wherever possible and with the builders in, you can't expect an artiste of my calibre to work with noise going on [[:|]] Well actually, I haven't seen them for over a week, but they might come in today and I would have to start some work only to have to stop because I've got a headache.

In any case I've still got a few DVDs that I haven't watched yet, so it must be time to stop work for the day.

DG

@Rob Elliott said:

Hey DG for us 'low-tech hacks' - could you tell me how to get my 4 slaves set up for this 3 gig switch. What is it exactly (soft or hardware). The .exe you mentioned.

My 4 machines all have 2 gig ram but range in age form 2 months to 2 years old (2.7 to 3.2 ghz).

Thanks for any help you can be on this.


Rob

It is all software based.

The switch is an alteration to the boot.ini file in order that Windows allows you to use up to 3GB for applications and 1GB for Windows as opposed to 2GB each. Even with only 2GB RAM there can be an advantage in using the switch (for me it was around 200MB of samples), but it can make the system unstable. I have sent all details to VSL and they are testing at the moment.

In the meantime, let me know what host you are intending to use on your VI machines.

DG


Hi DG,

I am using VStack on the VI PC's.


Rob

@Rob Elliott said:

Hi DG,

I am using VStack on the VI PC's.

Rob

As you'll see from my tests I managed to get V-Stack to load well over 2.5GB samples, but it is not really designed to do this so you could have crashes. I would recommend the 3GB switch in any case, but if you really want to try to load 2.8GB in V-Stack PM me, and I'll "talk" you through it.

FWIW the next version of Forte will be designed this way, so you might want to try that out when it is released.

DG

@Rob Elliott said:

Hi DG,

I am using VStack on the VI PC's.

Rob

As you'll see from my tests I managed to get V-Stack to load well over 2.5GB samples, but it is not really designed to do this so you could have crashes. I would recommend the 3GB switch in any case, but if you really want to try to load 2.8GB in V-Stack PM me, and I'll "talk" you through it.

FWIW the next version of Forte will be designed this way, so you might want to try that out when it is released.

DG

You're a great resource and help DG. Many thanks!!!!

Rob