Re: Windows 7 32 Convert 64-bit
Gema Shisila
Assuming the 64-bit value is a FILETIME value, it represents the number of 100-nanosecond intervals since January 1, 1601. The Java Date class stores the number of milliseconds since January 1, 1970. To convert from the former to the latter, you can do this:
I would like to convert 64-bit numbers stored as decimal integers to a hexadecimal representation.
I am aware of the eval command tostring(dec, "hex"). It works well enough but seems to be limited to 32-bit integers.
@helge, I tested on Splunk Enterprise 7.0 on Windows 10 64 bit and can see the issue with tostring(64bitInteger,"hex") converting to 32 bit Hexadecimal number. Please add a bug tag to your question and report the same to Splunk Support through your Splunk Entitlement.
If you installed the 32-bit version of Sage 100 on a computer running the 64-bit version of Windows, you can convert it to the 64-bit version. You should do this only if you are no longer using any earlier 32-bit versions of Sage 100 installed on the same computer, and if all of your Sage 100 workstations are running the 64-bit version of Windows.
I know how to partition (actually one of the solutions is to set /, /etc, /home, /var/www, and /opt as separate partitions) and I know that a clean install is way better than a dirty one, yet I would like to know if/how it's possible to do that.
On the other hand, what you requested is possible, there is a little guide for Debian based systems but remember "this really is for professional-level sysadmins" and "this procedure is, in every possible respect, a bad idea. If it eats your firstborn, please don't come crying to me"... (so good luck)
Upgrading from 32 to 64 bits without explodifying my system took me the better part of a week. Including manually fixing 600+ broken packages in aptitude, because the automatic resolver started looping, apparently due to PERL:i386 (required by installed packages) being incompatible with PERL:amd64 (required by the packages you are trying to install).
This was after I manually installed a bunch of packages, including the correct version of PERL, to fix an apt screwup: you see, apt-get -f install (which is required to get a mostly-working 64-bits system) will uninstall PERL32 in order to install PERL64... Then merrily proceed to try removing 1234 other packages before getting 'round to actually reinstalling PERL. Needless to say, this is not a good idea, when a sizable portion of the apt system (an lots of other things, really) depends on a working PERL.
The reinstallation was performed entirely from console (aptitude FTW, of course), because the console pretty much only requires a working bash (and working curses for aptitude, but if you try to do this, curses will be plentiful, you can bet on it), whereas X requires... Way too much stuff to trust it to keep working while you perform open heart surgery on your system.
You see, you now have multiple i386 packages that don't have an actual multiarch equivalent, so you will be stuck with various technically "unavailable" dependencies. You already have them installed, so your system will run, but at this stage... I wouldn't trust apt any farther than I can throw it.
One minor hiccup of this procedure is that it will cause portions of the apt system (and other critical subsystems) to be uninstalled partway through, causing errors during the remainder of the process (you don't say), and leaving you up the creek.
Note that, at least for me, the network stopped working at one... Well, several... Points. This was due to apt removing a number of packages that are necessary to keep your network working (such as your dhcp client).
Unless you have a wired nework (your WiFi packages have already been uninstalled, and WiFI is rather more complicated to get to work anyway), know its configuration information, and are able to use ifconfig, route, etc.
After apt is satisfied with the state of your system you can run aptitude and manually fix the 600 broken packages you will find. Apparently apt and aptitude have different ideas of what a working system looks like. Don't ask me why.
Also, as I mentioned, the aptitude resolver enters an infinite loop if you try to let it do its thing automatically. Can't blame it, really, it was designed to start on a working system and help the user add or remove some packages, not fix this kind of abomination.
If you don't know the difference between sync and rsync, if you aren't comfortable with insmod, if you don't know how to use ifconfig, if you don't routinely prefer aptitude to the graphical installer whose name escapes me at the moment... Just make a backup of your data and install from scratch.
This might be a much more reasonable thing to do once the multiarch spec is implemented. -- currently postponed to 11.04, but keep in mind it's been postponed for about 6 releases now. That said, actual progress was made in 10.10, so maybe it'll happen this time.
The terms 32-bit and 64-bit refer to the way a computer's CPU, handles information. The 64-bit version handles large amounts of RAM much better than a 32-bit system. If you are running a 32-bit version of Ubuntu, you can only perform an upgrade to another 32-bit version of Ubuntu. Similarly, if you are running a 64-bit version of Ubuntu, you can only perform an upgrade to another 64-bit version of Ubuntu.
You can now do this fairly easily with recent installers (at least with 13.10 which I just used). Boot into the 64-bit image DVD (or USB drive or whatever) and choose the first option to reinstall, keeping your personal files. This works even if you don't have a separate /home partition.
This will reinstall most of the system including apps, but it takes a list of your installed packages beforehand to reinstall them from repo, so as long as a package has a 64-bit version available to it at the time, you should end up with most of your apps when you reboot. In my experience a few didn't get installed - mainly those that had been installed through 3rd party repos such as Google Chrome - but it doesn't take long to install these manually afterwards.
I just tried the solution suggested above by Nick (Oct 19'13): Using the Ubuntu 64-bit Live CD to do a 64-bit reinstall.
I used the Ubuntu 14.04.4 Live CD. But if the first option is indeed called a "reinstall", it more precisely appears as:
To be real sure, I tried with a test disk, and indeed, the first thing the "reinstall" option does is to reformat the existing ext4 partition. No luck.
So I'm afraid the "upgrade in-place to 64-bit" solution Nick suggested doesn't exist anymore in 14.04.
And BTW, Canonical, I hardly see the point for the installer having both the so-called "reinstall" option and the "Erase disk and install" one. Both seem to do about the same thing.
You need to do a fresh install with the 64bit version of Ubuntu. It is possible to have 32bit windows and 64bit Ubuntu, as long as they are not sharing the same disk or partition, for obvious reasons. Refer to the documentation for howto on dual-booting.
The SAS PC Files Server is used to convert 32-bit Microsoft Office files to SAS 64-bit files. This SAS note explains both how to install the SAS PC Files Server and how to perform the 32-bit to 64-bit conversion. Please read the instructions completely, especially before downloading the SAS PC Files Server. You should make sure that your SAS TS Level and SAS PC Files Server versions match.
If you see version 9301.0.20145.58769 of the SAS PC Files Server and you have SAS 9.3 TS1M2, you can upgrade to the new SAS PC Files Server without uninstalling the earlier version. See SAS Note 47237 about how to upgrade the SAS PC Files Server.
If you are using the SAS PC Files Server on the same Windows X64 machine that SAS is running on, use the syntax below, where the SERVER= option is not required. If you are not running the SAS PC Files Server on the same machine as SAS, see the section "Importing and Exporting Microsoft Office Files When SAS and the SAS PC Files Server Are on Different Machines" or the section "If the SAS PC Files Server Is Running as a Manual Task," below.
To use the LIBNAME statement with an Excel file, use syntax as shown in the following example, the file extension varies depending on the type of Excel file (xls, xlsx, or xlsb) :libname test pcfiles path='drive:\yourdirectory\yourfile.xls';data temp1; set test.yoursheet;run;libname test clear;To import a Microsoft Access .MBD or .ACCDB database table, use the syntax as shown in the following example: PROC IMPORT DBMS= ACCESSCS OUT=yoursasdata REPLACE TABLE='youraccesstable'; DATABASE='drive:\yourdirectory\yourfile.mdb';RUN;To export to a Microsoft Access .MDB or .ACCDB database table, use syntax as shown in the following example: PROC EXPORT DATA=yoursasdata OUTTABLE="youraccesstable" DBMS= ACCESSCS REPLACE ; DATABASE="drive:\yourdirectory\yourfile.mdb"; RUN;To use the LIBNAME statement with a Microsoft Access file, use the following example: libname test pcfiles path='drive:\yourdirectory\yourfile.mdb';data temp1; set test.youraccesstable;run;libname test clear;Importing and Exporting Microsoft Office Files When SAS and the SAS PC Files Server Are on Different Machines or If the SAS PC Files Server Is Running as a Manual Task If you are running SAS on a different machine than the SAS PC Files Server, use the following code. Note that the port and server are required because SAS and the SAS PC Files Server are on different machines.
Im just trying to Open an Ae project (CS6) on my MAC (Mavericks) and its getting a message that project was created on windows 64 bit version 11 and must to convert it, but when agree the project shows messed up to work on it.
d3342ee215