Windows 10 Issues
 

Been flustered since moving to Windows 10... Everytime I try and load Prime 95 I get this error:

[QUOTE]
[Main thread Aug 11 23:37] Mersenne number primality test program version 28.5
[Main thread Aug 11 23:37] Optimizing for CPU architecture: Core i3/i5/i7, L2 cache size: 256 KB, L3 cache size: 6 MB
[Comm thread Aug 11 23:39] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:39] Unable to open log file.
[Comm thread Aug 11 23:39] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:39] Unable to open log file.
[Comm thread Aug 11 23:39] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:39] Unable to open log file.
[Comm thread Aug 11 23:39] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:39] Unable to open log file.
[Comm thread Aug 11 23:40] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:40] Unable to open log file.
[Comm thread Aug 11 23:40] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:40] Unable to open log file.
[Comm thread Aug 11 23:40] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:40] Unable to open log file.
[Comm thread Aug 11 23:40] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:40] Unable to open log file.
[Main thread Aug 11 23:40] Starting workers.
[Comm thread Aug 11 23:47] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:47] Unable to open log file.
[Comm thread Aug 11 23:47] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:47] Unable to open log file.
[Comm thread Aug 11 23:47] ERROR: Unable to open spool file.
[Comm thread Aug 11 23:47] Unable to open log file.
[Main thread Aug 11 23:51] Stopping all worker threads.
[Main thread Aug 11 23:51] Starting worker.
[Main thread Aug 11 23:51] Error creating worktodo.txt file
[Comm thread Aug 11 23:51] Error opening results file to output this message:
[Comm thread Aug 11 23:51] Unable to open log file.
[Comm thread Aug 11 23:51] Error creating worktodo.txt file
[Comm thread Aug 11 23:51] Unable to open log file.
[Main thread Aug 11 23:51] Starting workers.
[Main thread Aug 11 23:52] Error creating worktodo.txt file
[Comm thread Aug 11 23:52] Error opening results file to output this message:
[Comm thread Aug 11 23:52] Unable to open log file.
[Comm thread Aug 11 23:52] Error creating worktodo.txt file
[Comm thread Aug 11 23:52] Unable to open log file.
[/QUOTE]
Anyone see something blaringly obvious that I've missed? Thanks!

It is probably due to file permissions :blahblahblah: Did you transfer your data via a CD?

[QUOTE=paulunderwood;407764]It is probably due to file permissions :blahblahblah: Did you transfer your data via a CD?[/QUOTE]

No I upgraded through the interwebs.

[QUOTE=Sulamandora;407769]No I upgraded through the interwebs.[/QUOTE]

I have never done that, but the permissions on the folder and/or the files therein most likely have the wrong permissions. To set them you will have to right click when in "explorer" and tick some options. Prime95 already seems executable -- the others need a "write" permission. :smile:

[QUOTE=Sulamandora;407759]Been flustered since moving to Windows 10... Everytime I try and load Prime 95 I get this error:


Anyone see something blaringly obvious that I've missed? Thanks![/QUOTE]

I was just having some fun on a couple of my servers. I setup a new admin user (not the default admin) to use to login and run P95... This is on a Server 2012 R2 install, but probably similar.

Anyway, I forgot there are default policies that restrict certain things for admins that aren't the default admins (part of the whole messy UAC stuff). The directory I was running Prime95 from was relying on "admin" permissions since I was lazy and didn't configure them explicitly... I found out when it tried to write intermediate files or the results file/modify the worktodo... none of that worked.

So anyway, check all of that out. If in doubt, you could just run Prime95 with "run as administrator" and see if it makes any difference. If so, you can check the file permissions where you have it installed and make sure your specific user has full access (or just keep running it as administrator and call it good) :smile:

[QUOTE=Madpoo;407775]I was just having some fun on a couple of my servers. I setup a new admin user (not the default admin) to use to login and run P95... This is on a Server 2012 R2 install, but probably similar.

Anyway, I forgot there are default policies that restrict certain things for admins that aren't the default admins (part of the whole messy UAC stuff). The directory I was running Prime95 from was relying on "admin" permissions since I was lazy and didn't configure them explicitly... I found out when it tried to write intermediate files or the results file/modify the worktodo... none of that worked.

So anyway, check all of that out. If in doubt, you could just run Prime95 with "run as administrator" and see if it makes any difference. If so, you can check the file permissions where you have it installed and make sure your specific user has full access (or just keep running it as administrator and call it good) :smile:[/QUOTE]

Thanks! So it's definitely the permissions. I ran it as administrator and it works. I'll go in and manually set permissions later. Thank to both of you for the help!