Multi CPU installation using GUI client ?

willy1 · 2004-03-15, 23:36

I'm trying to set up a multi-CPU (4) installation under Windows, using the GUI client.

I initially ran the install program from the NFSNET folder using the GUI in 'visible' mode as documented.

I then created the processors/p1 thru processors/p3 folders, and copied and edited the config.txt files per the multi client instructions.

The problem starts when I need to start the 4 clients. Since the Gui needs a unique nfsGUI.ini file for each CPU, I copied the nfsGUI.exe to each px folder, started it, and ran the config on each one, pointing to the shared client folder and the unique px folder. I verified that each nfsGUI.ini file has the correct folder information.

When I start the GUI client from each folder, it always wants to use the project.in information in the p0 folder. If I start the second or third client, it just bombs, most likely because of the lock file in the p0 folder.

What's the trick to get 4 clients running?

willy1
Free-DC

Jeff Gilchrist · 2004-03-16, 01:32

Hi Willy,

Right now the GUI only supports controlling one instance of the client running at a time. You will have to start the 2nd, 3rd, and 4th one manually I'm afraid (or create shortcuts).

I never took into account SMP support when I wrote the GUI so if it sees any nfsnet client running it will change the "Start" button into a "Stop" button and not allow you to launch the clients properly.

The GUI and client itself are completely seperate programs and the nfsnet client can run without the GUI at all (the GUI is just a monitoring app). The way to launch a 4 clients at the same time would be to open 4 command prompts and run the same nfsnetclient.exe from each (or create a shortcut to the nfsnetclient.exe and double click on it 4 times which will launch 4 seperate instances of the clients). The lock files will get the client to use the correct directories for data.

In the future, the GUI should support SMP machines but that might not be until the next major release.

Jeff.

willy1 · 2004-03-16, 01:50

Thanks Jeff -

That's about the conclusion I came to.

I guess I'll have a bunch of DOS boxes lined up. No background or service mode, I gather?

willy1

Jeff Gilchrist · 2004-03-17, 21:19

Right, no service mode. Hopefully the next-gen client will support being installed as a service in Windows.

wblipp · 2004-03-18, 03:31

Quote:

Originally Posted by willy1

I guess I'll have a bunch of DOS boxes lined up. No background or service mode, I gather?

If it's Win2K or WinXP you can get rid of the DOS Boxes by starting with the Task Scheduler. This tip in described in the
ElevenSmooth Help; I assume it would work for NFSNET, too.

Jeff Gilchrist · 2004-03-18, 13:19

Hmmm very interesting. The scheduled tasks I guess launch the app without a console so it runs in the "background".

That I guess allows people to run software with service-like abilities but does not need to contain any kind of service code.

Thanks wblipp.

Jeff.

2004-03-15, 23:36	#1
willy1 Mar 2004 2 Posts	Multi CPU installation using GUI client ? I'm trying to set up a multi-CPU (4) installation under Windows, using the GUI client. I initially ran the install program from the NFSNET folder using the GUI in 'visible' mode as documented. I then created the processors/p1 thru processors/p3 folders, and copied and edited the config.txt files per the multi client instructions. The problem starts when I need to start the 4 clients. Since the Gui needs a unique nfsGUI.ini file for each CPU, I copied the nfsGUI.exe to each px folder, started it, and ran the config on each one, pointing to the shared client folder and the unique px folder. I verified that each nfsGUI.ini file has the correct folder information. When I start the GUI client from each folder, it always wants to use the project.in information in the p0 folder. If I start the second or third client, it just bombs, most likely because of the lock file in the p0 folder. What's the trick to get 4 clients running? willy1 Free-DC

2004-03-16, 01:32	#2
Jeff Gilchrist Jun 2003 Ottawa, Canada 3·17·23 Posts	Hi Willy, Right now the GUI only supports controlling one instance of the client running at a time. You will have to start the 2nd, 3rd, and 4th one manually I'm afraid (or create shortcuts). I never took into account SMP support when I wrote the GUI so if it sees any nfsnet client running it will change the "Start" button into a "Stop" button and not allow you to launch the clients properly. The GUI and client itself are completely seperate programs and the nfsnet client can run without the GUI at all (the GUI is just a monitoring app). The way to launch a 4 clients at the same time would be to open 4 command prompts and run the same nfsnetclient.exe from each (or create a shortcut to the nfsnetclient.exe and double click on it 4 times which will launch 4 seperate instances of the clients). The lock files will get the client to use the correct directories for data. In the future, the GUI should support SMP machines but that might not be until the next major release. Jeff. Last fiddled with by Jeff Gilchrist on 2004-03-16 at 01:35

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Installation of GGNFS	LegionMammal978	Msieve	17	2017-01-20 19:49
installation of OS trouble	wildrabbitt	Linux	5	2015-12-22 16:51
Don't know where installation folder went	jinydu	Information & Answers	10	2009-10-14 01:29
split a prime95 queue & client installation	joblack	Information & Answers	1	2009-01-06 08:45
Multi-Core / Multi-CPU Assignments (missing)	worknplay	Software	3	2008-11-05 17:26

2004-03-16, 01:50	#3
willy1 Mar 2004 2 Posts	Thanks Jeff - That's about the conclusion I came to. I guess I'll have a bunch of DOS boxes lined up. No background or service mode, I gather? willy1

2004-03-17, 21:19	#4
Jeff Gilchrist Jun 2003 Ottawa, Canada 495₁₆ Posts	Right, no service mode. Hopefully the next-gen client will support being installed as a service in Windows.

2004-03-18, 13:19	#6
Jeff Gilchrist Jun 2003 Ottawa, Canada 3·17·23 Posts	Hmmm very interesting. The scheduled tasks I guess launch the app without a console so it runs in the "background". That I guess allows people to run software with service-like abilities but does not need to contain any kind of service code. Thanks wblipp. Jeff.