Could 6.12.33 be the cause for my invalids?

Message boards : Number crunching : Could 6.12.33 be the cause for my invalids?
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1130173 - Posted: 20 Jul 2011, 19:11:23 UTC - in response to Message 1130165.  
Last modified: 20 Jul 2011, 19:14:16 UTC

try period_interation 10 or 12 instead

Something is seriously wrong somewhere. Your Wu's are failing after 17 seconds which means either something isn't installed correctly or your app_info isn't setup correctly.

I'd go for a reinstall using the Lunatics installer


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1130173 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1130200 - Posted: 20 Jul 2011, 20:11:42 UTC - in response to Message 1130165.  

Neither -period_iterations_num 2 (or other values) nor downgrading to Cat 11.2/SDK2.3 seem to make any difference.

I've got the HD5750 which has only 9 Compute Units @ 700 MHz.

For my Sapphire HD5750 with 1GB I use: -instances_per_device 1 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096

I was using 11.2 without any computing problems. However, I have gone back to 10.12 due to a weird HDMI issue I have with the 11.x drivers.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1130200 · Report as offensive
Acrklor
Volunteer tester
Avatar

Send message
Joined: 22 Oct 01
Posts: 14
Credit: 639,144
RAC: 0
Austria
Message 1130207 - Posted: 20 Jul 2011, 20:54:21 UTC - in response to Message 1130173.  

try period_interation 10 or 12 instead

I don't know what good that will do after trying several differnt values already...anyway, it didn't change a thing.
Neiter did Lunatics reinstallation.

For my Sapphire HD5750 with 1GB I use: -instances_per_device 1 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096

AstroPulse is working fine so far, the problem is only with MultiBeam.
"Judging people you don't know for things you don't understand is just really stupid." - Ellen Page
ID: 1130207 · Report as offensive
Profile Mike Special Project $75 donor
Volunteer tester
Avatar

Send message
Joined: 17 Feb 01
Posts: 34258
Credit: 79,922,639
RAC: 80
Germany
Message 1130217 - Posted: 20 Jul 2011, 21:24:31 UTC
Last modified: 20 Jul 2011, 21:26:19 UTC

You are also trashing a lot of units at beta as i noticed.
I think its best we try in german on weekend if you want.

You can PM me any time.


With each crime and every kindness we birth our future.
ID: 1130217 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1130222 - Posted: 20 Jul 2011, 21:33:25 UTC - in response to Message 1130207.  
Last modified: 20 Jul 2011, 21:53:32 UTC

Can you try the non-HD5 version of r177 please, and if that doesn't work please drop CLinfo.exe into a Cmd window, run it, and post the output,

Claggy
ID: 1130222 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1130228 - Posted: 20 Jul 2011, 21:45:12 UTC
Last modified: 20 Jul 2011, 21:47:07 UTC

Please copy and paste my app_info for the HD5 into your app_info. replacing what you currently have. It appears that something was editted incorrectly in yours. Notice that mine doesn't start with app version. If you've installed from the lunatics installer you'd have gotten this same setup.


<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 12 -instances_per_device 2</cmdline>
<file_ref>
<file_name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels.cl</file_name>
<copy_file/>
</file_ref>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
</app_version>

make sure this is placed before the final /app_info


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1130228 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1130277 - Posted: 21 Jul 2011, 0:07:03 UTC - in response to Message 1130207.  

try period_interation 10 or 12 instead

I don't know what good that will do after trying several differnt values already...anyway, it didn't change a thing.
Neiter did Lunatics reinstallation.

For my Sapphire HD5750 with 1GB I use: -instances_per_device 1 -unroll 12 -ffa_block 8192 -ffa_block_fetch 4096

AstroPulse is working fine so far, the problem is only with MultiBeam.

*bonks head* right. I guess my mind was somewhere else.
I have been using -period_iterations_num 5 for MB. I'll try your setting of -period_iterations_num 14 later tonight and see what happens. Maybe that value is jsut a bit to much for these cards. We shall see.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1130277 · Report as offensive
Acrklor
Volunteer tester
Avatar

Send message
Joined: 22 Oct 01
Posts: 14
Credit: 639,144
RAC: 0
Austria
Message 1130389 - Posted: 21 Jul 2011, 14:13:29 UTC

You are also trashing a lot of units at beta as i noticed.

That's right...as I said my first post.

I think its best we try in german on weekend if you want.

Why? Is my English that bad? :)

Can you try the non-HD5 version of r177 please

Didn 't work, only seemed to change the seconds after which the unit is aborted.

please drop CLinfo.exe into a Cmd window, run it, and post the output

Here it comes:
Number of platforms:				 1
  Platform Profile:				 FULL_PROFILE
  Platform Version:				 OpenCL 1.1 ATI-Stream-v2.3 (451)
  Platform Name:				 ATI Stream
  Platform Vendor:				 Advanced Micro Devices, Inc.
  Platform Extensions:				 cl_khr_icd cl_amd_event_callback cl_amd_offline_devices cl_khr_d3d10_sharing


  Platform Name:				 ATI Stream
Number of devices:				 2
  Device Type:					 CL_DEVICE_TYPE_GPU
  Device ID:					 4098
  Max compute units:				 9
  Max work items dimensions:			 3
    Max work items[0]:				 256
    Max work items[1]:				 256
    Max work items[2]:				 256
  Max work group size:				 256
  Preferred vector width char:			 16
  Preferred vector width short:			 8
  Preferred vector width int:			 4
  Preferred vector width long:			 2
  Preferred vector width float:			 4
  Preferred vector width double:		 0
  Native vector width char:			 0
  Native vector width short:			 0
  Native vector width int:			 0
  Native vector width long:			 0
  Native vector width float:			 0
  Native vector width double:			 0
  Max clock frequency:				 970Mhz
  Address bits:					 32
  Max memory allocation:			 134217728
  Image support:				 Yes
  Max number of images read arguments:		 128
  Max number of images write arguments:		 8
  Max image 2D width:				 8192
  Max image 2D height:				 8192
  Max image 3D width:				 2048
  Max image 3D height:				 2048
  Max image 3D depth:				 2048
  Max samplers within kernel:			 16
  Max size of kernel argument:			 1024
  Alignment (bits) of base address:		 32768
  Minimum alignment (bytes) for any datatype:	 128
  Single precision floating point capability
    Denorms:					 No
    Quiet NaNs:					 Yes
    Round to nearest even:			 Yes
    Round to zero:				 Yes
    Round to +ve and infinity:			 Yes
    IEEE754-2008 fused multiply-add:		 Yes
  Cache type:					 None
  Cache line size:				 0
  Cache size:					 0
  Global memory size:				 536870912
  Constant buffer size:				 65536
  Max number of constant args:			 8
  Local memory type:				 Scratchpad
  Local memory size:				 32768
  Kernel Preferred work group size multiple:	 64
  Error correction support:			 0
  Unified memory for Host and Device:		 0
  Profiling timer resolution:			 1
  Device endianess:				 Little
  Available:					 Yes
  Compiler available:				 Yes
  Execution capabilities:				 
    Execute OpenCL kernels:			 Yes
    Execute native function:			 No
  Queue properties:				 
    Out-of-Order:				 No
    Profiling :					 Yes
  Platform ID:					 00000000012A9568
  Name:						 Juniper
  Vendor:					 Advanced Micro Devices, Inc.
  Driver version:				 CAL 1.4.1016
  Profile:					 FULL_PROFILE
  Version:					 OpenCL 1.1 ATI-Stream-v2.3 (451)
  Extensions:					 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_printf cl_amd_media_ops cl_amd_popcnt cl_khr_d3d10_sharing 


  Device Type:					 CL_DEVICE_TYPE_CPU
  Device ID:					 4098
  Max compute units:				 4
  Max work items dimensions:			 3
    Max work items[0]:				 1024
    Max work items[1]:				 1024
    Max work items[2]:				 1024
  Max work group size:				 1024
  Preferred vector width char:			 16
  Preferred vector width short:			 8
  Preferred vector width int:			 4
  Preferred vector width long:			 2
  Preferred vector width float:			 4
  Preferred vector width double:		 0
  Native vector width char:			 16
  Native vector width short:			 8
  Native vector width int:			 4
  Native vector width long:			 2
  Native vector width float:			 4
  Native vector width double:			 0
  Max clock frequency:				 2666Mhz
  Address bits:					 64
  Max memory allocation:			 1073741824
  Image support:				 No
  Max size of kernel argument:			 4096
  Alignment (bits) of base address:		 1024
  Minimum alignment (bytes) for any datatype:	 128
  Single precision floating point capability
    Denorms:					 Yes
    Quiet NaNs:					 Yes
    Round to nearest even:			 Yes
    Round to zero:				 Yes
    Round to +ve and infinity:			 Yes
    IEEE754-2008 fused multiply-add:		 No
  Cache type:					 Read/Write
  Cache line size:				 64
  Cache size:					 32768
  Global memory size:				 3221225472
  Constant buffer size:				 65536
  Max number of constant args:			 8
  Local memory type:				 Global
  Local memory size:				 32768
  Kernel Preferred work group size multiple:	 1
  Error correction support:			 0
  Unified memory for Host and Device:		 1
  Profiling timer resolution:			 384
  Device endianess:				 Little
  Available:					 Yes
  Compiler available:				 Yes
  Execution capabilities:				 
    Execute OpenCL kernels:			 Yes
    Execute native function:			 Yes
  Queue properties:				 
    Out-of-Order:				 No
    Profiling :					 Yes
  Platform ID:					 00000000012A9568
  Name:						 Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz
  Vendor:					 GenuineIntel
  Driver version:				 2.0
  Profile:					 FULL_PROFILE
  Version:					 OpenCL 1.1 ATI-Stream-v2.3 (451)
  Extensions:					 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_media_ops cl_amd_popcnt cl_amd_printf cl_khr_d3d10_sharing 


Please copy and paste my app_info for the HD5 into your app_info. replacing what you currently have. It appears that something was editted incorrectly in yours.

You suggested I reinstall with the Lunatics Installer, which I did, which means my actual app_info comes directly from the Installer. And I don't think there is something wrong with that.

Notice that mine doesn't start with app version.

Obviously I left that part and the AstroPulse part out.

If you've installed from the lunatics installer you'd have gotten this same setup.

I don't think so...the default settings from the lunatics installer are not '-period_iterations_num 12 -instances_per_device 2'. It looks more like this...here is the whole app_info:
<app_info> 
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>AK_v8b_win_x64_SSE41.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
           <file_name>AK_v8b_win_x64_SSE41.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
           <file_name>AK_v8b_win_x64_SSE41.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>AstroPulse_Kernels_r521.cl</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>506</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_intelx86</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 1 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_intelx86</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 1 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>506</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_x86_64</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 1 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_x86_64</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 1 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.05r409_SSE.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
            <file_name>ap_5.05r409_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>    
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
            <file_name>ap_5.05r409_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>MultiBeam_Kernels_r177.cl</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
        <platform>windows_intelx86</platform>
        <avg_ncpus>0.05</avg_ncpus>
        <max_ncpus>0.05</max_ncpus>
        <plan_class>ati13ati</plan_class>
        <cmdline>-period_iterations_num 5 -instances_per_device 1</cmdline>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>MultiBeam_Kernels_r177.cl</file_name>
            <open_name>MultiBeam_Kernels.cl</open_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
        <platform>windows_x86_64</platform>
        <avg_ncpus>0.05</avg_ncpus>
        <max_ncpus>0.05</max_ncpus>
        <plan_class>ati13ati</plan_class>
        <cmdline>-period_iterations_num 5 -instances_per_device 1</cmdline>
        <coproc>
            <type>ATI</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>MultiBeam_Kernels_r177.cl</file_name>
            <open_name>MultiBeam_Kernels.cl</open_name>
            <copy_file/>
        </file_ref>
    </app_version>
</app_info> 

"Judging people you don't know for things you don't understand is just really stupid." - Ellen Page
ID: 1130389 · Report as offensive
Profile skildude
Avatar

Send message
Joined: 4 Oct 00
Posts: 9541
Credit: 50,759,529
RAC: 60
Yemen
Message 1130466 - Posted: 21 Jul 2011, 17:27:51 UTC - in response to Message 1130389.  

As I stated before remove he following portion from your app_info.

<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</name>
<executable/>
</file_info>
<file_info>
<name>MultiBeam_Kernels_r177.cl</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 5 -instances_per_device 1</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r177.cl</file_name>
<open_name>MultiBeam_Kernels.cl</open_name>
<copy_file/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.05</max_ncpus>
<plan_class>ati13ati</plan_class>
<cmdline>-period_iterations_num 5 -instances_per_device 1</cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>MB_6.10_win_SSE3_ATI_HD5_r177.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>MultiBeam_Kernels_r177.cl</file_name>
<open_name>MultiBeam_Kernels.cl</open_name>
<copy_file/>
</file_ref>
</app_version>

and inset what I've previously posting in its place. It is a working version of my app_info for the HD5 ATI app. I had to manipulate the app_info myself when I installed because it did something similar. I assumed it had something to do with the other versions for the ATI app included in the app_info. When I removed the extra lines I was able to run without a problem. See if that works. You've tried everything else.


In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope
ID: 1130466 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1130493 - Posted: 21 Jul 2011, 19:13:53 UTC - in response to Message 1130389.  
Last modified: 21 Jul 2011, 19:14:36 UTC

You are also trashing a lot of units at beta as i noticed.

That's right...as I said my first post.

I forgot to change my settings to the same as your last night. Today I changed to <cmdline>-period_iterations_num 12 -instances_per_device 1</cmdline> and everything looks like it has been going along fine. When I get home from work tonight I'll bump up to 14 and see what happens. If that goes OK I will upgrade to Cat 11.5 like you are using.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1130493 · Report as offensive
Acrklor
Volunteer tester
Avatar

Send message
Joined: 22 Oct 01
Posts: 14
Credit: 639,144
RAC: 0
Austria
Message 1130532 - Posted: 21 Jul 2011, 20:28:52 UTC

I had to manipulate the app_info myself when I installed because it did something similar. I assumed it had something to do with the other versions for the ATI app included in the app_info. When I removed the extra lines I was able to run without a problem. See if that works. You've tried everything else.

Didn't think the app_info could need additional changes right after the Installation.

You've tried everything else.

Obviously I didn't...because I found the problem while trying a few things on my own: VirtualStore. I know how this Vista/7-feature works, however I don't know why BOINC triggered it...there where some workunits and a few slot folders there, which at least could be responsible for every odd behaviour. Removing the BOINC folder from VirtualStore was the solution, of course.

The VirtualStore folder was created right after installing 6.12.33.
In any case I was not able to provoke the use of the VirtualStore again.

Thanks again for the suggestions.
"Judging people you don't know for things you don't understand is just really stupid." - Ellen Page
ID: 1130532 · Report as offensive
Previous · 1 · 2

Message boards : Number crunching : Could 6.12.33 be the cause for my invalids?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.