optimized sources

[Jason G]

Right -
  to unhide Application Data folder in x64 I did the following

- Start a command prompt [ Change to whichever drive has the "Documents and Settings" folder ]
- cd \Documents and Settings\<your username>
- attrib -h "Application data"
(don't forget the quotes)

now it should show next time you try to browse there or do a 'DIR' at the command prompt

Jason

[_heinz]

The performance_doku is now in our test-repository. It is worth to have a look at it...
You can find some important knowledge out of the HPC (High Performance Computing) world.
Attention if you work via a phone line, some files are not even small.
Have fun to explore it.
modify: I made a directory structure for better browse and acess for the phone-line user

heinz 

[_heinz]

Hey Heinz!, remember about the SVN Autoproperties thing at:
http://lunatics.kwsn.net/5-windows/stock-sah-v6-build-notes-so-far.msg6174.html#msg6174

In Vista the directory is:
\Users\<your user name>\AppData\subversion

have done this SVN Autoproperties thing
now it works and makes the update 

a lot of data are transfered to make the SVN update now on the V8-Xeon
I thought it would go easier, copied all files on a usb-stick, then on the V8-Xeon,
at first this shows great, it shows the green symbol, then I maked update...now all files are uploaded again...
.. but I have time...as long as the line are good...no problem...

heinz

[_heinz]

4870 x2 with 2x 800 Stream Processing Units is now available in germany, price 449,00 €
Technische Daten
Chipsatz der Grafikkarte:  Radeon HD4870 X2 
Grafikkartenspeicher:  2048MB 
Speicherinterface:  256 bit 
Taktung der GPU in MHz:  750 
Taktung des Speichers in MHz:  3600 
RAMDAC:  2x 400 Mhz 
PCI-e x16:  Ja 
Steckplatz der Grafikkarte:  PCIe x16 
Anschlüsse der Grafikkarte:  2x DVI 
TV-Out:  Ja 
Max. Auflösung:  2560x1600 
Direct-X Version der Grafikkarte:  10.1 
Farbtiefe:  32 bit 
Crossfire Support:  Ja 
Kühlung der Grafikkarte:  aktiv 
Verpackung:  Retail 
 
weitere Informationen
Technische Daten:

- 2x ATI HD 4870 Grafikchip mit 750MHz
- 2048MB GDDR5 3600MHz Speichertakt
- DirectX 10.1 Unterstützung
- Shader Model 4.1
- PCI-Express 2.0 x16
- 2x 800 Stream Processing Units
- 2x 256-bit Memory Interface
- 400MHz RAMDAC
- Dual-Link DVI mit HDCP / TV-Out / HDMI durch Adapter (nicht im Lieferumfang)
- CrossFireX™
- ATI AvivoTM HD
- PowerPlay™-Stromspar Technologie
- Kühlung: aktive Dual-Slot Lösung
- Display Port Unterstützung
- Windows Vista ™ Premium Ready
----------------------------------------------------------------------------------------------------------
It shows us where we should go in our  hpc-development process

heinz

[Jason G]

see post I just made in other thread 

[_heinz]

News from the V8-Xeon:
Fedora9_x86_64 is installed now on the SKT parallel to Vista64 on the second disk.
heinz

Today fedora9 runs several hundred of updates, although I installed the latest stable version.
here is a look at fedora systemmonitor during the update process.
After the updates I must still install the ATI graphic-driver for HD3870.
With the standard driver the resolution is not high enough and the fonts look out blurred.
Perhaps I need a monitor file too, but I have'nt...it uses generic..
heinz

[_heinz]

What a adventure with the ATI-graphic driver.
After download the file ati-driver-installer-8-7-x86.x86_64.run  into a central location I logged in a terminal as su and started it with the command
./ati-driver-installer-8-7-x86.x86_64.run
it worked and started as here
after I have this done (standard) the system said the driver is not properly installed please run aticonfig from a terminal as su
or if xserver fails run aticonfig --initial -f  from console.

after I typed the commands
./aticonfig --initial=dual-head --screen-layout=above
./aticonfig --dtop=horizontal --overlay-on=1
./aticonfig --resolution=0,1600x1200,1280x1024,1024x768
./aticonfig --force-monitor=crt1,notv
./aticonfig --tv-geometry=85x90+10-10
./aticonfig --list-adapters
it shows "0"

./aticonfig --adapter=0 --initial

./startx

it says now:
logfile: "/var/log/Xorg.0.log"
using configfile: "/etc/X11/xorg.conf"
dlopen: "/usr/lib64/xorg/modules/drivers//fglrx_drv.so"  :undefined Symbol: miZeroLineScreenIndex
(EE) Failed to load "/usr/lib64/xorg/modules/drivers//fglrx_drv.so"
(EE) Failed to load module fglrx (loader failed 7 )
(EE) No drivers available
Fatal Server errors
No screens found
giving up   

and run aticonfig --initial -f   did not help
---------------------------------------
a second install and configure get the same result.....uhhhh what a pain...
the system starts and xstart fails, it stand then on the console login

looks like a new install, but then I have the same problem, no the actual ATI driver and still small resolution...
did not expected such a trouble with fedora9....and the ati-driver...

heinz

[_heinz]

After some tries to install the driver again, allways same error...
A rescue of the system did not help....startx did not start sucessful..
I started a complete new installation...on the formated disk..
After this was done and the system comes up, and the update process started -->
37 security updates
330 bugfix updates
29 enhancement updates.....
download and installation runs 5 hours....
I had never thought that such a lot of updates must be done, my download was newest version from 14.05.2008 when Fedora9 was published. Better no comment to this...
---------------------------------------------
Fedora  release 9(Sulphur), RedHat nash version 6.0.52 is now up again.
kernel: 2.6.25-14.fc9.x86_64

The problem with the monitor resolution is not solved...must read some fora comments, I think the system did not known my TFT-monitor-specific values like max possible resolutions etc..., the manufacturer Medion is unknown....it takes generic, so resolution of 1280x1024 and some others are  not available.
What we can do ?  maybe to edit the monitor file....
Very angry.....

Why I do this ?? All for our testbed...and development systems....
heinz

[Jason G]

Hi Heinz,
   Back ~14 years ago we had to recompile the kernel just to get a network card running, and manually configure the monitor and video card files too,  and some video card manufacturers outright refused to release details / driver code. later it was found they were doing dodgy stuff like skipping frames to make the refresh appear faster. 

Is fedora close enough to any other distros that they may have a more suitable driver package etc? were all your monitor specs supplied with your monitor? maybe you can tailor configuration files from an existing model that is close.

Dunno, we used to have to do it all manually, but that was way before modern window managers, so maybe this is no longer possible?  Good luck.

Jason

[_heinz]

Hi Jason,
the toaster is alredy on in the V8-Xeon thread, FB-DIMM1-temps of 101°C are monitored, have a look there

heinz

[Jason G]

Hi Heinz,
   That seems rather incredible.  Have you got some kind of thermometer to put it there so you can see if that is anywhere near accurate?

[_heinz]

Hi Heinz,
   That seems rather incredible.  Have you got some kind of thermometer to put it there so you can see if that is anywhere near accurate?

The only thing is the sensor of the case, which i placed between the 2 FB-DIMMs, in the last 5 minutes this sensor goes down from 71 to 65°C, after I ended the measuruing with the programms Everest, CPUID-Hardwaremonitor and Processexplorer.
A temp of 65°C looks normal for me. Roomtemp = 25,7°C.
Very interesting that measuring increase the FB-DIMM temp so much, what do you mean to this hypothese ? Can this be ?
I started short Everest to look up
FB-DIMM = 76°C
FB-DIMM1 = 94°C
FB-DIMM2 = 87°C
looks like normal, as I had have before
--------------------------
looks like the hypothese is true. 
hmmm.. very interesting   
edit: I looked up in the wu's, as the temp goes down to 65, I had a couple of this short 15 min wu's running
now my case FB-DIMM-sensor shows  again 71°C
FB-DIMM = 76
FB-DIMM1 = 96
FB-DIMM2 = 88
at this moment are 8 wu's  running with a duration of 1h:01min
but the values look now better, seems ok,.

heinz

[_heinz]

Killed several times my multiboot by using Acronis Disk Director Suite and OS-Selektor. 
Now some support requests are open...
OS-Selector quitted his work...
Always Fedora9 was booting...
from there I edited the file bootwiz.oss   ..after this was done Vista64 starts again
Get now MBR Error3 at start 
Must still fix it, but Vista boots again..Linux is dead...Grub shows some sites of laughing masks  rofl
several tries to fix grub dont have sucess...
A lot of trouble with all this multiboot....
Have now latest Open Suse 11.0 und Fedora9 as DVD and Knoppix ready for install

heinz

[_heinz]

Fixed the MBR Error 3
With a Rescue Disk assembled with Acronis  I was able after some adventuries to reinstall and activate OS-Selektor again.
This multiboot stuff is really a very complex thematic.
At the moment are installed and working:
disk1: Windows Vista64
disk2: Fedora9 ...
disk3: free for data
no raid active..

heinz

[_heinz]

Hi Jason,
to get compatibility with several softwarepackages I ordered a additional OS "Windows XP Professional x64 Edition" , which has a sticker "English with German and Japanese Multilingual User Interface CD" .
This OS I installed today on the V8-Xeon into a separate 60GB free partition on the first disk. Installation runs as usual, I choosed german for keyboard and language, but wounder when it starts it shows english-surface. ? uuhh...

Second: the system XP Prof 64 does not recognize the networkadaptor from board DX5400XS.
Vista64 shows this networkadaptor which is properly installed.
I have not expected to get this error in the network installation.
Its a pain to have latest hardware and the system did not install properly because some drivers are not found on the install medium.
cry...   
Sure I can set in a second better known network-card.... as 3com etc...but thats not my thing.

Third is to say: after the installation of XP, Vista did not start anymore(this I have expected). So I started with the Vista DVD to repair the start-area and wounder what it shows:
Diagnostic and reparation details:
The startsector of the systempartition is damaged.
Repair action: boot sector repair
Result: sucessful
Errorcode = 0x0
----------------------
so far OK, Vista64 starts again but the bootmenue as I know from NT4-Server and XP is not shown anymore.

Next step is to look up for drivers from Intel...then try again...
There is still some research todo to get a full functional multiboot machine..with several different windows and several different linux installations.

heinz