(archive)mfaktXapp 1.4 - Page 7

Stef42 · 2012-10-26, 11:51

It seems that the latest version of mfakXapp does not work with Windows 8.
Error: 'Value either too large or too small for Win32''.
Adding and staging work does not work at all, starting and exiting does not work either. You got any idea?

swl551 · 2012-10-26, 12:52

Quote:

Originally Posted by Stef42

It seems that the latest version of mfakXapp does not work with Windows 8.
Error: 'Value either too large or too small for Win32''.
Adding and staging work does not work at all, starting and exiting does not work either. You got any idea?

Sounds pretty bad!

I'd start by deleting/renaming the existing mfaktxappconfig.txt file and then starting the app. It should take you into config editor. Try adding one location and leave all other defaults. see what happens.

The entire app is .NET 3.5 so I would not expect total failure as you described... BUT Windows 8 is new.

Keep me informed I'll do what I can.

Stef42 · 2012-10-26, 13:38

I works perfectly with only one instance running. I can add work, assign to worker, export and update stats fine. I soon as I add a second directory, mfaktXapp goes bad. It can still assign work, giving the ''Value is either too large or too small for Win32'' warning. I can see in both directory's that the worktodo.txt files have the correct number of tasks. The program just won't start nor update properly.

Secondly, the CTRL+C function does not work anymore. The sendcontrolsignal start's [with administrator rights] but nothing happens. Starting .bat files is working good.

swl551 · 2012-10-26, 13:45

Quote:

Originally Posted by Stef42

I works perfectly with only one instance running. I can add work, assign to worker, export and update stats fine. I soon as I add a second directory, mfaktXapp goes bad. It can still assign work, giving the ''Value is either too large or too small for Win32'' warning. I can see in both directory's that the worktodo.txt files have the correct number of tasks. The program just won't start nor update properly.

Secondly, the CTRL+C function does not work anymore. The sendcontrolsignal start's [with administrator rights] but nothing happens. Starting .bat files is working good.

If you remove the first instance and leave only the second and get the same error it suggests a bogus value in one of the Factor lines. This is important since it tries to calculate GHZzdays based on factor, from, to. If anyone of those is bogus that error is possible.

CTRL-C relies on the exact process name as found in taskManager. Verify Win8 did not tack on something like (-compat) to the name. What you find in taskmanager is what you use.

Stef42 · 2012-10-26, 13:52

I tried with both instances, both work fine when only one of them is used in mfaktXapp. So, both directory's are clean.

The name of the process in the Task Manager is still "mfaktc". It worked good in the past, using Windows 7. It's not working now anymore.

swl551 · 2012-10-26, 14:01

Quote:

Originally Posted by Stef42

I tried with both instances, both work fine when only one of them is used in mfaktXapp. So, both directory's are clean.

The name of the process in the Task Manager is still "mfaktc". It worked good in the past, using Windows 7. It's not working now anymore.

If it works in Win7 then we are really talking about what did MS change in Win8. Answers I do not have. I do not plan on using Win8 anytime soon so I won't be able to do any direct debugging on Win8.

kracker · 2012-10-26, 14:13

Yes, I noticed a while back that Ctrl+C and a few other things didn't work at all on Win8..(this was dev preview, lol) I just thought, "Meh, probably just a windows bug, Hey, it's still on beta."
If you need any testing on Win8 in the future, I *might* be getting win8, maybe

swl551 · 2012-10-26, 14:16

Quote:

Originally Posted by kracker

Yes, I noticed a while back that Ctrl+C and a few other things didn't work at all on Win8..(this was dev preview, lol) I just thought, "Meh, probably just a windows bug, Hey, it's still on beta."
If you need any testing on Win8 in the future, I *might* be getting win8, maybe

I tried running Prime95 on Win8 preview. No-go. That's the day I put my Win7 drive back into the computer.

Stef42 · 2012-10-26, 14:19

I can run Prime95 fine, I fact it's running right now on some P-1 assignments.

swl551 · 2012-10-26, 14:27

Quote:

Originally Posted by Stef42

I can run Prime95 fine, I fact it's running right now on some P-1 assignments.

Definetely fixed since the preview.

swl551 · 2012-10-26, 14:39

Quote:

Originally Posted by Stef42

I tried with both instances, both work fine when only one of them is used in mfaktXapp. So, both directory's are clean.

The name of the process in the Task Manager is still "mfaktc". It worked good in the past, using Windows 7. It's not working now anymore.

Did the SMTP emailer work OK for you?

2012-10-26, 11:51	#67
Stef42 Feb 2012 the Netherlands 2·29 Posts	It seems that the latest version of mfakXapp does not work with Windows 8. Error: 'Value either too large or too small for Win32''. Adding and staging work does not work at all, starting and exiting does not work either. You got any idea? Last fiddled with by Stef42 on 2012-10-26 at 11:52

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
(archive)MISFIT	swl551	MISFIT	584	2013-03-19 20:13
(archive)mfaktXapp 1.1.4 released	swl551	MISFIT	64	2012-09-15 22:08
Archive 2 for Other results (>155)	em99010pepe	Octoproth Search	161	2007-06-08 21:31
Archive 1 for Other results (>155)	ValerieVonck	Octoproth Search	90	2007-03-21 01:01
The Archive...	Xyzzy	Lounge	11	2003-03-31 20:42

2012-10-26, 13:38	#69
Stef42 Feb 2012 the Netherlands 58₁₀ Posts	I works perfectly with only one instance running. I can add work, assign to worker, export and update stats fine. I soon as I add a second directory, mfaktXapp goes bad. It can still assign work, giving the ''Value is either too large or too small for Win32'' warning. I can see in both directory's that the worktodo.txt files have the correct number of tasks. The program just won't start nor update properly. Secondly, the CTRL+C function does not work anymore. The sendcontrolsignal start's [with administrator rights] but nothing happens. Starting .bat files is working good.

2012-10-26, 13:52	#71
Stef42 Feb 2012 the Netherlands 2×29 Posts	I tried with both instances, both work fine when only one of them is used in mfaktXapp. So, both directory's are clean. The name of the process in the Task Manager is still "mfaktc". It worked good in the past, using Windows 7. It's not working now anymore.

2012-10-26, 14:13	#73
kracker "Mr. Meeseeks" Jan 2012 California, USA 2³×271 Posts	Yes, I noticed a while back that Ctrl+C and a few other things didn't work at all on Win8..(this was dev preview, lol) I just thought, "Meh, probably just a windows bug, Hey, it's still on beta." If you need any testing on Win8 in the future, I might be getting win8, maybe

2012-10-26, 14:19	#75
Stef42 Feb 2012 the Netherlands 2·29 Posts	I can run Prime95 fine, I fact it's running right now on some P-1 assignments.