Windows 7 and all my Java stuff.
in [Java Programming]
|
From: Roedy Green on 22 Nov 2009 19:18 On Sun, 22 Nov 2009 14:46:51 -0800, Steve Sobol <sjsobol(a)JustThe.net> wrote, quoted or indirectly quoted someone who said : >Nah, you usually have the option of making a "recovery disk" set >yourself. The recovery disk set, if you need to use it, will restore >your computer to the condition it was in when you bought it; this means >a reinstall of Windows, your computer's specific drivers and all of the >software originally bundled with the computer. IIRC this is not that useful. Your partitions are undone. You lose all your data too. It also requires that a special partition be undamaged. There things you can recover with the Windows OS disk that don't require a complete reinstall. I think they are trying to prevent piracy, and they are not willing two enforce unique activation keys. What bugs me is vendors advertise that "Windows 7" is included. It isn't if you don't get a Windows 7 DVD. Acer does this. If you have any problem that want you to ship the entire machine to be fixed. You go without your machine for two months or so. You have no choice but to buy a Windows CD, or a whole new computer. -- Roedy Green Canadian Mind Products http://mindprod.com Finding a bug is a sign you were asleep a the switch when coding. Stop debugging, and go back over your code line by line.
From: Steve Sobol on 22 Nov 2009 22:06 In article <qukjg5918bo20o9er855j0uu8d8blfa9p5(a)4ax.com>, see_website(a)mindprod.com.invalid says... > IIRC this is not that useful. Your partitions are undone. You lose > all your data too. It also requires that a special partition be > undamaged. Depends on the manufacturer. I've never had to do a System Recovery on my Dells, but my HP allows me to do a non-destructive System Recovery. You need to reinstall your apps, but your data is left alone. > Acer does this. If you have any problem that want you to ship the > entire machine to be fixed. You go without your machine for two > months or so. You have no choice but to buy a Windows CD, or a whole > new computer. Then don't buy Acer. Dell sells PC's with other service plans, and I have no appreciable amount of experience with other brands, but I'd imagine they do too. -- Steve Sobol, Victorville, California, USA sjsobol(a)JustThe.net
From: Thomas Pornin on 23 Nov 2009 08:54 According to DuncanIdaho <Duncan.Idaho2008(a)googlemail.com>: > The question is, will all my Java stuff (Tomcat 6, Eclipse/My Eclipse > 5.1/ Java 1.6)that I currently have installed on my remaining XP SP2 > machine still work or do I need to get everything in new, spanky 64 bit > versions. The 64-bit versions of Windows are quite good at running the 32-bit applications. 32-vs-64 problems occur when trying to mix compiled binary code in the same address space. In the Java world, this means that if you run a 64-bit JVM then the JVM will dynamically translate the code into a 64-bit address space, which is fine, until you try to load a 32-bit DLL for native code, in which case the loading fails. Therefore it is most probable that running all your 32-bit apps "as is" in Windows will "just work", but you will shun the advantages of 64-bit computing; also, some applications may somehow complain about being roughly copied and not "installed" in the Windows sense of the term. Java code itself (the .class and .jar) are bit-size-neutral, they are loaded unchanged regardless of whether the JVM is 32-bit or 64-bit or whatever else. That is the whole point of Java. Hence, unless you explicitly use native code, Tomcat should run fine on a 64-bit JVM. The 64-bit address space may imply a slight increase in memory consumption because internal pointers get larger. But this is unlikely to have any real impact in most situations (most of the memory used in a typical application is for non-pointer data, e.g. byte[] or char[], which keeps the same size in a 64-bit JVM); also, Sun's JVM has an option to use 32-bit pointers in 64-bit mode ('-XX:+UseCompressedOops'). On the other hand, the extra and larger registers unlocked by 64-bit mode give a performance boost to some specific operations (in particular BigInteger, which runs about 3 times faster). And anyway, you will have to go 64-bit at some time, so better do it now. --Thomas Pornin
From: Roedy Green on 23 Nov 2009 13:14 On 23 Nov 2009 13:54:01 GMT, Thomas Pornin <pornin(a)bolet.org> wrote, quoted or indirectly quoted someone who said : >most of the memory used in a >typical application is for non-pointer data, e.g. byte[] or char[], In my own code, Strings and arrays of pointers to Strings would be the most common ram hog. I wonder if someone could cook up a simple tool to predict the effect of going to 64 bit on any given app. -- Roedy Green Canadian Mind Products http://mindprod.com Finding a bug is a sign you were asleep a the switch when coding. Stop debugging, and go back over your code line by line.
From: David Lamb on 23 Nov 2009 19:39
Thomas Pornin wrote: >(most of the memory used in a > typical application is for non-pointer data, e.g. byte[] or char[], > which keeps the same size in a 64-bit JVM) Do you have any studies that show this (ie. that most memory use is large arrays of this sort)? I came from an environment where tree-structured data (with lots of pointers) was common. |