our goose is cooked

[Nflight]

It isn't resolved yet and even my single 64 bit 3500+ will not conitune to run the application. I am getting a NON-Responding action every 90 seconds, that is all it will run till it seizes.
Majestic 12 - If you have resolved these issues already please advise!

[NeoGen]

I never heard of problems with dual cores and the .net platform... are you running 64 bit windows?

[Majestic-12]

Nflight: I have never heard of such issues. Do you run Windows XP 64-bit or is it normal 32-bit version?

Also, have you installed .NET 1.1 Service Pack 1 from here - http://www.microsoft.com/downloads/d...displaylang=en

Don't assume you have got it - download it and try to install, if its installed then it will refuse to continue, its a critical service pack that is totally necessary for node's operations as it fixes memory leaks.

Do you have any other computer to try node on? I just want to locate source of issues - whether its PC/OS or network.

[Nflight]

My 3500+ is running the 32 bit version of windows.
My 4200+ is running the 64 bit version of windows.

Oh and by the way I uninstalled the version on the 3500+ because it was locking up after just 84 seconds. NO clue why all this happens and everyone can run the blasted things?
I am still in there and willing to work it out if I can but I can't fiddle a whole day on the program away Like I did today! :cry:

I have found that I can get the program to work on my 3500+ system in the text mode only, if this helps! The GUI does not like when the screensaver is initialized ( I run a blank screen in 60 seconds from inactivity) and this was just blowing the program up, it could never recover! I am now on this list, but this is for about 2 hours in a day of struggling, not a full 24 hours of work!

http://www.majestic12.co.uk/projects...minfo.php?id=2

[Majestic-12]

It sounds like problem with video drivers - what video card have you got and are you running official WCQL (I think that's how they called) drivers?

[Nflight]

Majestic -12 (alex if thats you) I have overcome my errors with the help of Evil Dragon and my own stepping back and looking at the whole picture and writing down my mistakes and errors.
After reveiwing what I did and what I initially should be expecting, I discovered I made some dumb alterations. I reveiwed the screenshots on the Majestic Forum and altered mine to mimick those screenshots and found the system works best now after all errors were corrected.

Under Computer Management - Device Manager I am running two NVidia Ge Force 6600 GT's ( 2 video outputs per card for an effective 4 display capability, great tools ) Everything is up to date on the drivers.

Dumb errors by yours truly, I jumped before I looked over what I was jumping !

Thank you for the concern and also for the quick response.

[Majestic-12]

Good to hear its solved - thanks to Evil Dragon for this!

But what did you change to make it work?

[Nflight]

What did I change to make it work. . . .
Well I had to revert back to Microsoft thinking that everything in action is reverse in thinking, if you are a MCP you understand that jibberish.

More is not always better and opening the valves full bore is not always a good idea, also since I had no idea how this particluar crunching data operation works I figureed since my system can handle the excessive work load I would throw everything I could at it and wait to see what happens.

BAD idea, re-regulating the upstream and downstream to be 100% is not always a good thing due to the hungry bandwidth this project is. I have read over the forums between you (alexc and Evil Dragon) about the Newbie User settings and also the Geek Settings enhancement edition to be finished soon I hope. This would be a lot better if us crazed DC-er's had an idea of what this project needs then to fiddle so much and make the headaches roar with downtime. I made the mistake of seeing the chance to move everything to above nomall settings and run the operation at full speed I thought would be better.

Better explanation is needed to help make this project run more efficient. Better accessibility to the Screen Shots like a link on the main page (SCREENSHOT) with a "start here" flashing beside it. Have newbie settings and Geek settings.

[PCZ]

Nflight

I guess you moved the priorites to above normal, bad mistake.

But those settings should not be be there, a DC project should run on low.
If it is a bursty type like CB for example, then below normal is acceptable.

If you have another DC project running you might want to set MJ12 to below normal but be aware that if you only have one CPU this can slow your PC to a crawl.

[Nflight]

Thanks for the advice there PCZ, I actually have two machines one 3500+ and another 4200+. What I can't quite figure out is that the 3500 machine runs at twice the speed of the 4200. Go figure and the settings are the same on each.

Yes I found out that lower is better even with the uploading of the data barrel the smaller the units the faster the upload.
As for slowing my machines down to a crawl, I prey they produce a program that can do that, at the moment I have only seen the BSOD once on the 4200, and once on the 3500 as well.

Any more help would be greatly appreciated there PCZ!