Thanks, but that was not really the problem. My problem was that my XF86(which I installed myself on redhat 7 now use/etc/X11/XF86Config-4 and not/etc/X11/XF86Config to configure the XServer.And XF86Config-4 did not have any modeline at all. So I pasted the modelines from XF86Config to XF86Config-4 and now it works. Wierd
But how do you X to generate a resolution over 85Hz? I run XFree8.3 and used XConfigurator to generate the config, but it insist on runnig 85Hz and not 120Hz as it should. XConfigurator does detect my screen correct, and my screen(And my windows install) are able to run 120Hz, but I can't make XFree do that -(
It is almost imposible to by any quality laptop widtout windows. That is the entire point with the case. You are forced to by windows even if you don't want it. That is the reason you can get your mony back.
You seem to forget that posix is just a description of what functions a system must implement(If it want to support posix) and how theese functions must behave. It is not a system description.
Posix is(shuld be) a subset of LSB meaning that a LSB system should support posix, not the other way around.
Posix have been implemented on hurd,*Nix,linux qnx 6,amiga os(Almost, but contain some problems with the filesystem functions, and fork) and I also think that beos got a posix layer. (Oh and windows got posix support too, you just can't use it together with other windows functions, so that support is rather pointless)
There are absolut problems with opening documents written in Word 97. Far from always but sometimes it just really fuckup the margin when opening in Word2000. It's really wierd, but it behave as if the left margin must be 30% of the page size.
Well the problem is that my Mac don't have gcc installed. The only MacOS development i do is in Java. And I really don't want to install xx MB just to get the release notes for gcc. The release notes for gcc 3.3 from gnu does only mention 64 bit powerpc suported by aix.
Ofcause apple might have made their own modifications to gcc 3.3 and then released that compiler as gcc 3.3
I even did a google search on 64bit pointers macos but the only thing I found were descriptions about how to use more then 4G of ram with 32bit pointers.
So if Apple does allow applications to use more then 4GB address space they really have hidden the fact for many people. see for example: http://www.osnews.com/story.php?news_id= 3981 http://www.theregister.co.uk/content/39/3160 0.html
but if you could post your gcc 3.3 release note I wolud be happy.
(from: http://developer.apple.com/technotes/tn/tn2086.htm l )
-mcpu=970 This allows the compiler to use instructions only available on the G5 (also known as 970) processor.
-mpowerpc64 In combination with the above flags, this flag tells the compiler to enable the G5's native 64-bit long long support for greatly enhanced performance when working with long longs. At times, the -force_cpusubtype_ALL flag may also be needed.
See it says native 64-bit for long long. Nothing about pointers. I have been unable to find ANY reference to 64bit pointers anyware at developers.apple.com or other places talking about mac G5.
So while it might be posible to generate code with 64 bit pointers, i don't think malloc will ever give you a pointer abowe 4G.
So I would be glad to have any reference to any
documentation/story where ANYONE say they use 64bit memory references with MacOS X10.2.7 or 10.3
You might notice that the photoshop they used to demo the G5 only had 32bit pointers and used some bridge hardware(segments of a kind) to map the memory similary(but not as hacked as the Intel Xeon chip)
But THAT require a 64bit os. What use is it that your application use 64bit pointers if all the pointers you get from the os is only 32bit?
Besides using the -mpowerpc64bit flag does NOT allow your compiler to use 64 bit pointers with any current version of MacOS/gcc. What -mpowerpc64does is that it allows gcc to generate native 64bit ppc code to your long long variables.
AmigaDos always used 32 bit. The the 68000 hardware used in Amiga 500,600 and 2000 only supported 24 bit ram, so the highest 8 bit were of no pratical use until you got a 68020 or better.
And the name is AmigaOS not AmigaDos. AmigaDos is the filesystem part of AmigaOS
But do we actuelly know that the os CAN run 64 bit apps? The photoshop they mention does use a hack similary to the Intel Xeon in order to access more then 4GB ram, but that might just be because they did not have time to make photoshop 64bit safe.
There is so significant oil produktion in iraq right now. Most of the people who (used to)work with oil production are afriad to leave their home.(Still to many uncontrolled people)
Or they could just paste a copy of the gpl on all the nukes. Remember on only the ones who receive a copy of the gpl software can ask for a copy of the source, and after beeing hit by a nuke you don't ask about the source anyway.
Slashdot Mirror
But no os does yet have any good support for that feature for normal programs which just run in a window -(
So killing someone just because you belive he did something wrong is ok?
What happend to the justice system?
How do you order an new mac widtout a harddisk?
Noone ever said that linux was the most stable design either. I wish we were all running hurd or qnx6 insted :-}
I think they are talking about drivers. With the current windows design any driver that crash have a good change of taking the os down with it.
Thanks, but that was not really the problem. My problem was that my XF86(which I installed myself on redhat 7 now use /etc/X11/XF86Config-4 and not /etc/X11/XF86Config to configure the XServer.And XF86Config-4 did not have any modeline at all. So I pasted the modelines from XF86Config to XF86Config-4 and now it works. Wierd
Redhat is not a commercial software companies. They are a consultent company who also package software so they have something to consult.
But how do you X to generate a resolution over 85Hz?
I run XFree8.3 and used XConfigurator to generate the config, but it insist on runnig 85Hz and not 120Hz as it should. XConfigurator does detect my screen correct, and my screen(And my windows install) are able to run 120Hz, but I can't make XFree do that -(
Martin
And to make things even worse
ssh myhost.com -p2300 is legal BUT
ssh afile User@myhost.com:/Someware -P2300
is NOT legal.
No version of qnx is using Mach. qssl made their own kernal. For qnx6 that kernal is called Neutrino 2.
And even photon(The gfx system) is using c bindings, so I really don't think they have used much c++.
Martin
It is almost imposible to by any quality laptop widtout windows. That is the entire point with the case. You are forced to by windows even if you don't want it. That is the reason you can get your mony back.
You seem to forget that posix is just a description of what functions a system must implement(If it want to support posix) and how theese functions must behave. It is not a system description.
Posix is(shuld be) a subset of LSB meaning that a LSB system should support posix, not the other way around.
Posix have been implemented on hurd,*Nix,linux qnx 6,amiga os(Almost, but contain some problems with the filesystem functions, and fork) and I also think that beos got a posix layer. (Oh and windows got posix support too, you just can't use it together with other windows functions, so that support is rather pointless)
Martin
But then it can't have been that bad for him can it?
There are absolut problems with opening documents written in Word 97. Far from always but sometimes it just really fuckup the margin when opening in Word2000. It's really wierd, but it behave as if the left margin must be 30% of the page size.
Well the problem is that my Mac don't have gcc installed. The only MacOS development i do is in Java. And I really don't want to install xx MB just to get the release notes for gcc. The release notes for gcc 3.3 from gnu does only mention 64 bit powerpc suported by aix.
= 39810 0.html
Ofcause apple might have made their own modifications to gcc 3.3 and then released that compiler as gcc 3.3
I even did a google search on 64bit pointers macos but the only thing I found were descriptions about how to use more then 4G of ram with 32bit pointers.
So if Apple does allow applications to use more then 4GB address space they really have hidden the fact for many people. see for example:
http://www.osnews.com/story.php?news_id
http://www.theregister.co.uk/content/39/316
but if you could post your gcc 3.3 release note I wolud be happy.
Martin
Could you please provide an url?
Martin
(from: http://developer.apple.com/technotes/tn/tn2086.htm l )
-mcpu=970 This allows the compiler to use instructions only available on the G5 (also known as 970) processor.
-mpowerpc64 In combination with the above flags, this flag tells the compiler to enable the G5's native 64-bit long long support for greatly enhanced performance when working with long longs. At times, the -force_cpusubtype_ALL flag may also be needed.
See it says native 64-bit for long long. Nothing about pointers. I have been unable to find ANY reference to 64bit pointers anyware at developers.apple.com or other places talking about mac G5.
So while it might be posible to generate code with 64 bit pointers, i don't think malloc will ever give you a pointer abowe 4G.
So I would be glad to have any reference to any documentation/story where ANYONE say they use 64bit memory references with MacOS X10.2.7 or 10.3
You might notice that the photoshop they used to demo the G5 only had 32bit pointers and used some bridge hardware(segments of a kind) to map the memory similary(but not as hacked as the Intel Xeon chip)
MartinBut THAT require a 64bit os. What use is it that your application use 64bit pointers if all the pointers you get from the os is only 32bit?
Besides using the -mpowerpc64bit flag does NOT allow your compiler to use 64 bit pointers with any current version of MacOS/gcc. What -mpowerpc64does is that it allows gcc to generate native 64bit ppc code to your long long variables.
Yes, but each TASK can still only use 4GB of ram. (OR use a hack similary to the Intel Xeon but that is ugly)
AmigaDos always used 32 bit. The the 68000 hardware used in Amiga 500,600 and 2000 only supported 24 bit ram, so the highest 8 bit were of no pratical use until you got a 68020 or better.
And the name is AmigaOS not AmigaDos. AmigaDos is the filesystem part of AmigaOS
But do we actuelly know that the os CAN run 64 bit apps? The photoshop they mention does use a hack similary to the Intel Xeon in order to access more then 4GB ram, but that might just be because they did not have time to make photoshop 64bit safe.
Martin
There is so significant oil produktion in iraq right now. Most of the people who (used to)work with oil production are afriad to leave their home.(Still to many uncontrolled people)
I am waiting for the hardware itself. Then I can make a benchmark using the software I use. That would be usefull.
The obvious reason would be if you had any application that required more then 3GB of ram.
Or they could just paste a copy of the gpl on all the nukes. Remember on only the ones who receive a copy of the gpl software can ask for a copy of the source, and after beeing hit by a nuke you don't ask about the source anyway.