Is 32-bit okay?

I'm in the proces of downloading the CS6 Master Collection onto a 32-bit Dell. Is that going to work? If not the whole collection, will parts of it work?
Thanks!
Tree

Yes, parts of it will work including Photoshop, Illustrator, InDesign, Dreamweaver but not After Effect, Premiere Pro, AME, Encore, Speedgrade, OnLocation and what have you. refer to the tech specs of the individual programs for more clarification.
Mylenium

Similar Messages

Network bridging two cable connections. Worth it?

I tend to be a bit (okay excessively) power hungry. My apartment complex provides a free shared wireless cable connection. I found it to be not reliable with uptime and was forced to get a dedicated cable line for myself.
Then I had this thought: when there are times when this wireless and free connection is up and running, would it be worth it to bridge the two connections on my desktop? One would be wired, the other wireless. I haven't yet purchased the wireless card since I'd like some input on this first. Both are cable connections at around 6 mbps (Comcast). I'm fairly savvy with networks however not so much on this concept of bridging in home computing. I use the Internet for large downloads, FTP, SSH, and web design, and I'm just power hungry , so I'm curious what the bandwidth and speed increases would be on this.
My desktop is very powerful and new, if that were to at all be a concern. Any thoughts, experiences, or input on this?
Last edited by jskier (2007-08-15 12:22:37)

Lone_Wolf wrote:
It sounds like you want to combine both physical nics into 1 virtual, this is called bonding.
Download the kernel sources and check Documentation/networking/bonding.txt .
I've done a bit of searching and it seems that downloading large files , ftp and such don't benefit from this as they only can make one connection.
Everyhting that uses multiple connections like p2p should benefit from it.
If you're going to use this, you should consider installing a downloadmanager like prozilla or aria / aria2.
Hmm, me thinks I'll play around with it, thanks!

Publish to repository Grayed out in IDT

Hello All,
I am unable to publish to repository in IDT. I undertand one needs to publish the connection first...but even its grayed out.
I was told I have full access.Since i am new to IDT i may have missed to do something prior to publishing ?
Any inputs highly appreciated.
Thanks.

Hi
I am also have same issue. To publish the universe to repository , it will take lot of time,
But universe changes will reflect into the webi immediately,
We requested network team and they have increase bandwidth and now little bit okay.
So please check with your network team.

Help: krtld error - amd64 kernel failing to load

Greetings,
I'm running the SXDE 1/08 snv_79b X86 release of Solaris and the amd64 bit kernel is suddenly failing to load, instead I get the message:
krtld: bind_primary() : no relocation information found for module /platform/i86pc/kernel/amd64/unix
krtld: error during initial load/link phase
krtld could neither locate nor resolve symbols for :
/platform/i86pc/kernel/amd64/unix
in the boot archive. Please verify that this file matches what is found inthe boot archive.
You may need to boot using the solaris failsafe to fix this.
Unable to boot.
Press any key to reboot.
The menu.lst boot parameters are:
kernel$ /platform/i86pc/kernel/$ISADIR/unix
module$ /platform/i86pc/$ISADIR/boot_archive
where $ISADIR = amd64
I can boot into 32 bit okay still but will need to get 64 bit working again.
Can someone please advise me on what I need to do to fix this?
Thanks :)
John

It has happened again.
It seemed to fix itself the first time but has encountered exactly the same error.
Does anyone have any ideas?
BTW I'm actually running the SXDE 1/08 snv_79a X86 release of Solaris not 79b
Regards,
John

Recording what you hear on the comp

Well I got cubase but everytime i export the song the sounds are all different and ultimately the song sounds completely different then it was on the program, and even if i figured out how to fix this, i still have the problem of converting it a different format. So, instead of doing the two i was hoping to see if there is any way i can record what i hear on the computer. I tried and i didnt find a way and hoping someone here could guide me... i got an Audigy 2 Value and Windows XP if that is of any help. It be very appreciated if someone could help me. Thanks

which version of cubase are you using? as i dont use the home pakages im not 100% on if evertythings the same but im sure this will be! what export function are you using? and what is the input channel selected recording in the computers audio devices! if you select the input as waves that might help the "what you hear" recording outside of cubase.
use said you are using only midi files i agree with jutapa about using the vsti's if you read the cubase manual you will find that it mentions something about not being about to mixdown outside midi functions with out syncing the device cubase or something along those lines!
i didn't pay all that much attention as it's never been a problem for me!
here the part of the manual on mix down
The Export Audio Mixdown function in Cubase SX/SL allows you to mix
down audio from the program to a file on your hard disk, in a number of
formats. You can choose to mix down one of the following:
An output bus.
For example, if you have set up a stereo mix with tracks routed to a stereo output bus,
mixing down that output bus would give you a mixdown file containing the whole mix.
Similarly, you can mix down a complete surround bus, either to a single multi-channel
file (interleaved) or to one file per surround channel (split).
The channel for an audio track (Cubase SX only).
This will mix down the channel for the track, complete with insert effects, EQ, etc. This
can be useful for turning a number of events into a single file, or if you are using CPUintensive
insert effects – by exporting the track and re-importing it into the project you
can turn off the insert effect, saving processor power.
Any kind of audio channel in the mixer (Cubase SX only).
This includes VST Instrument channels, effect return channels (FX Channel tracks),
Group channels and ReWire channels. There are many uses for this – for example, you
can mix down an effect return track or turn individual ReWire channels into audio files.
Notes
The Export Audio Mixdown function mixes down the area between the
left and right locator.
When you mix down, you get what you hear – mutes, mixer settings
and insert effects are taken into account.
Note though that you will only include the sound of the bus or channel you select for
mixdown.
here's the bit okay seems you can't record midi in the mix down at all you have to record it like a normal audio file first. that's just with the record button on to a normal audio track you'll have to figure out how to get your midi to feed through into cubase
the way i do it is only leave the information out to the midi device plugged in and then plug the analog out put of the device into the input that cubase will record this will make sure cubase records the file as an audio file with out getting a cross over of the midi information being sent(i hope that makes sence some times i can make a muddle of explaining things). there are other ways to do this but this ways nice and simple and lazy! and works just aswell as any other.
MIDI tracks are not included in the mixdown!
To make a complete mixdown containing both MIDI and audio, you first need to record
all your MIDI music to audio tracks (by connecting the outputs of your MIDI instruments
to your audio inputs and recording, as with any other sound source).
With Cubase SX, you can also export selected tracks – this is a different
function that doesn’t create an audio mixdown.
Rather, this is a way to transfer complete tracks (including clips and events) from one
project to another
i left everything else in just in case you wanted to check through it!
1. Set up the left and right locator to encompass the area that you want
to mix down.
2. Set up your tracks, so that they play back the way you want.
This includes muting unwanted tracks or parts, making manual mixer settings and/or
activating the R (Read) automation buttons for some or all mixer channels.
3. Pull down the File menu and select “Audio Mixdown…” from the
Export submenu.
The Export Audio Mixdown dialog appears.
The upper half of this dialog is a standard file dialog, while the lower
half contains file format options and settings for the mixdown function.
Note that the available settings and options differ depending on the
selected file format
Select the bus or channel you want to mix down with the Outputs popup
menu (with Cubase SL you can only export busses, not channels).
This lists all output busses and channels in the active project.
5. Select the channel configuration for the mixdown file with the
Channels pop-up menu.
Typically you would select the same channel configuration as the bus or channel you’re
mixing down, but it’s also possible to e.g. mix down a stereo bus to a mono file. In this
case a warning will appear, asking if that’s what you want to do.
Here you will also find the “N. Chan. Split” and “N. Chan. Interleaved” options – these
allow you to create a surround mixdown file, either as one mono file per surround channel
– split – or as a single multi-channel file – interleaved (Cubase SX only).
The Channels pop-up and the “N. Chan” options are only available when
an uncompressed file format is selected (AIFF, uncompressed Wave,
Wave64 or Broadcast Wave).
For the other formats you can select stereo or mono using controls that are specific to
each format. When mixing down to 5.1 Surround, you also have the option to mix down
to Windows Media Audio Pro (Windows and Cubase SX only) – see page 670.
6. Select a file format with the File type pop-up menu.
7. Make additional settings for the file to be created.
This includes selecting sample rate, resolution, quality, etc. The available options depend
on the selected file format – see page 660.
8. If you want to automatically import the resulting audio file back into
Cubase SX/SL, activate the “Import to” checkboxes.
If you activate the “Pool” checkbox, a clip referring to the file will appear in the Pool.
Activating the “Audio Track” checkbox as well will create an audio event that plays the
clip, and place it on a new audio track, starting at the left locator.
The Import options are only available if you have selected an uncompressed
file format (AIFF, uncompressed Wave, Wave64 or Broadcast
Wave files).
9. If you activate Real-Time Export, the export will happen in real time, i.e.
the process will take the same time as regular playback.
Some VST plug-ins require this to have time to update correctly during the mixdown –
consult the plug-in manufacturers if uncertain.
CUBASE SX/SL
Export Audio Mixdown 27 – 659
When Real-Time Export is activated, the exported audio will be played
back on the Audition bus.
The fader below the Real-Time Export checkbox allows you to adjust the volume of the
Audition bus.
10.If you activate Update Display, the meters will be updated during the
export process.
This allows you to check for clipping, for example.
11.Select a folder and a name for the audio file to be created.
With some file formats you can create split stereo files (see page 661).
This will create two files (one for each side) with the same name, but
with the letter “L” appended for the left channel file and “R” for the right
channel file.
In the same way, split multi-channel (surround) files (Cubase SX only) will have the
same name followed by a number indicating the surround channel.
12.Click Save.Depending on the file format, an additional dialog may appear.For example, when exporting to MP3 format a dialog appears where you can add infoabout the song title, artist, etc. Make the desired
settings and click OK to proceed.A dialog with a progress bar is displayed while the audio file is created.If you change your mind during the file creation, you can click theAbort button to abort the operation.if you
have activated any of the “Import to” options, the file will be importedback into the project.When playing back the re-imported file in Cubase SX/SL, remember to mute the originaltracks so that you really hear the true result.
hope thast helps

Kernel panic, can't start with install disc or safe mode

Two days ago my 2008 Mac Pro got a green screen that froze up the entire system. After a few minutes I decided to force power down by holding the power button. Since then I receive a kernel panic every time I boot up in Mac OS.
I run bootcamp and I'm able to boot up Vista 32 bit okay. After the system went down my video card, NVidia 8800GT, was no longer being loaded in Windows due to and error (43). I tried installing old drivers, new drivers, and today I finally bought a new video card, NVidia GTX 285 Mac. The new card works great in Windows, but I'm still unable to load up Mac OS.
I've tried resetting the PRAM. I've also tried booting up off of the 10.5 install disc to try a fresh install, but I get kernel panics even when I do that. I connected the Mac to another Mac using target disc mode and using Verify Disk it detected no errors. I used the Apple Hardware Test and again the Mac detected no problems. I've reseated the RAM in the cpu and disconnected all usb and firewire devices. I've called Apple support and they told me to do all of these things I just mentioned. After all of that I even tried erasing the Mac HD partion of the hard drive thinking that it might erase a problematic file or at least let me do an install on a fresh drive (thankfully I made an exteral backup of all my Mac files when I had it in target disk mode). I'm at a loss of what else to try other than taking it into a mechanic. Has anyone experienced this before or have any ideas?

Your OS X system sounds hosed. However, getting a kernel panic trying to start from an installer disc is usually a good sign of hardware failure. If you aren't using the original installer disc that came with the computer, then that could be a problem - wrong version for the machine. Or the installer disc itself is defective.
If your Boot Camp partition is on a different drive, then I'd suspect the hard drive but you believe it's OK. This could be a problem with RAM. However, I would look for another suitable installer disc you can try that boots the same version of OS X that was installed originally on your machine.

Does Anyone Else Have PC Crashing With Photoshop?

This is by far my most serious problem. It started with CS5 and still crashes with CS6.
On intensive or involved Photoshopping, my system will frequently and suddenly bluescreen. This happens ONLY when I'm working with Photoshop. I'm not sure whether to blame Adobe or Topaz Labs, as I use Topaz filters extensively. Upgrading my video driver yesterday didn't help.
PC
MSI 990FXA-GD80 Motherboard
AMD Phenom II X6 1100T CPU
8 Gigs DDR3 RAM
Asus nVidia GTX550 Video w. 1Gig RAM
OCZ Solid 3 60 Gig SATA III Solid State Drive
Western Digital 750 Gig SATA III Hard Drive
OCZ 750 Watt 80 Plus Power Supply
Windows 7 Professional 64 Bit
Okay, it has nothing to do with the 64 bit software as CS5 was 32 bit and it would bluescreen occasionally.
There's no telling when or if my system will bluescreen. A week or so ago, I got it to repeat a bluescreen while editing a Topaz generated graphic image. However, I tried playing with that same graphic yesterday and it didn't bluescreen.
My next step is to spend an hour or so editing the heck out of an image and NOT using Topaz filters.
Anyhow, I just wondered if anyone has had similar problems or any comments on using Topaz filters.
Gerry

Well now I have two replies which pretty much cancel each other out. As I stated above, I spent a lot of time editing the heck out of a photo and not using any help from Topaz filers. I couldn't get my edit to cause a bluescreen, however let me add my edit sure lends a new definition to the word abstraction.
I'm going to somehow go on a Topaz free sabbatical and see what happens. In addition, I've asked Topaz what video cards they use in their development PC's. Good luck getting an answer on that one.
<sigh> It never ends does it?
Gerry

Kinda scares me a bit.. okay.. maybe a LOT.. X(

I noticed something in my iPod. Whenever it accesses it's hard drive, apart from the super slight rumbling (which is normal), I hear a really tiny click right before it plays a song or video that I JUST selected, but this matter doesn't occur when I shuffle songs. This happens when I select and play a new song, even if the previous song it was playing isn't yet halfway through(not like in the shuffle mode where it finishes first your song before it plays another if you choose not to press next). I figure, maybe it's because it's locking the hard drive so it can save the files in case you drop it or something or it's maybe because it selects a new file and needs to access the hard drive again. I hope someone can confirm that everything's normal.
Danke,
--Rob
Message was edited by: kerobi11

A slight clicking noise whenever the hard drive is accessed is completely normal. It's the read/write arm moving into place.

Re: ATI HD 2600 PRO WINDOWS 7 64 BIT BOOTCAMP DRIVER ERROR

Okay - I *think* I was able to get the modified INF to work properly now - it turns out there were many more instances where changes needed to be made that my original procedure did not address. The updated procedure is below with additional steps added.
Procedure to manually update iMac Radeon HD 2600 PRO video card under Windows 7 (64 bit).
Rationale:
> Boot Camp drivers incorrectly identify the video card my 24" iMac (Dual core; 2.8 GHz - graphics card is shown as a "ATI Mobility Radeon HD 2600 XT") - this has been a long-standing problem when using my iMac under Boot Camp. There have been reports about how to update the drivers manually by obtaining them from ATI/AMD then installing them.
Background:
> When I was previously running Windows XP, I was able to perform the graphics driver update per the online instructions, without any problems.
> When I updated to Windows 7, 64-bit (because I was updated my Mac OS to 10.7 [Lion] and Windows XP was no longer supported in Boot Camp), I could no longer update the graphic card drivers to the Win7 64-bit version (it was giving an error that the driver was not supported).
> The solution I finally came upon was to modify the installer .INF file that comes with the drivers from AMD. I take no credit for this, except from the fact that I adapted a procedure I found for doing this for graphics cards in notebooks. The original place I found this is here <http://forum.notebookreview.com/gaming-software-graphics-cards/370695-guide-upda ting-your-ati-drivers-manually.html>.
NOTE & DISCLAIMER: I don't claim to fully understand every step that is going on here, nor if every step is needed. I based this on the procedure referenced in link immediately above and it seems to be working for me (that is, my graphics card driver was updated for Win7, 64-bit just like had been previously under WinXP) - YMMV.
>> This procedure was done with the AMD Radeon™ Desktop Video Card Drivers for "64 bit Windows Vista/Windows 7 "; Version 11.7, posted 2011-07-27 (main page: http://support.amd.com/US/Pages/AMDSupportHub.aspx)
1. Driver only was downloaded from AMD.
2. Downloaded file was installed to default location: C:\ATI
3. Gather info about the graphics card:
a. Open the Device Manager (Start>Computer [right-click]>Properties)
b. Expand the "Display Adapters" item to reveal the GPU (mine was listed as "ATI Mobility Radeon HD 2600 XT")
c. Right-click on the GPU and select "Properties"
d. Click the "Details" tab in the Properties window.
e. Click the drop-down under "Property" (top item should say "Device description) - find the item in the list that says "Hardware Ids"
>> There were four values for my card, shown below:
PCI\VEN_1002&DEV_9583&SUBSYS_0083106B&REV_00
PCI\VEN_1002&DEV_9583&SUBSYS_0083106B
PCI\VEN_1002&DEV_9583&CC_030000
PCI\VEN_1002&DEV_9583&CC_0300
f. Right click on the first value and select "Copy" - paste it into a separate document.
g. Go back and click the drop-down under "Property" - find the item in the list that says "Inf section" (it was far down the list).
h. Copy the value shown there and paste into a separate document; my value read: ati2mtag_M76
4. Modify the INF file from AMD:
a. First thing I did was make a copy of the directory containing the files that were installed in step 2 (located at C:\ATI) - my directory was called "11-7_vista64_win7_64_dd".
b. Go into this path: C:\ATI\Support\11-7_vista64_win7_64_dd\Packages\Drivers\Display\W76A_INF
c. Find the INF files (icon is a document with a gear on it), that start with "C7..." and "CH..." (mine were called "C7122569" & "CH122569").
d. Open the "C7..." file (it opens in Notepad).
e. The first thing I did was find and replace all existing instances of "M76" in the INF (I arbitrarily replaced it with the following value "M7a6"). There are a number of existing references to this property type in the original INF.
> I do not know if this is absolutely necessary but I found that it helped me to distinguish what was originally there with what I was modifying.
f. Do a "Find" command for "ATI Radeon HD 2600 PRO" (if you search for a shorter phrase, be aware there are other "2600 PRO" cards in the list).
> The exact line I found was <"ATI Radeon HD 2600 PRO" = ati2mtag_RV630, PCI\VEN_1002&DEV_9589>
g. Replace that line with the Inf section value and the first Hardware ID value, using the same format as the original line. The new entry I made read (notice that each successive entry has an addition <space> between the end of 'PRO' and the ending double quote):
"ATI Radeon HD 2600 PRO" = ati2mtag_M76, PCI\VEN_1002&DEV_9583&SUBSYS_0083106B&REV_00
"ATI Radeon HD 2600 PRO " = ati2mtag_M76, PCI\VEN_1002&DEV_9583&SUBSYS_0083106B
"ATI Radeon HD 2600 PRO " = ati2mtag_M76, PCI\VEN_1002&DEV_9583&CC_030000
"ATI Radeon HD 2600 PRO " = ati2mtag_M76, PCI\VEN_1002&DEV_9583&CC_0300
h. Next do a find for all instances of "ati2mtag_RV630"; for every instance you will need to replace that value with " ati2mtag_M76".
i. Next do another find for "RV630" and make sure to replace all instances with "M76" (this is to catch the couple of places where it doesn't have the "ati2mtag" prefix)
j. Close the file, saving your changes.
k. Repeat steps 4d - 4i, using the "CH..." file.
> I personally do not think this is needed since I believe the "C7…" INF is for Windows 7 and "CH…" is for Vista, but I modified both anyway.
5. Update the graphics driver using the modified INF files:
a. Go back to the Device Manager and expand the "Display Adapters" item again to show the "ATI Mobility Radeon HD 2600 XT" GPU
b. Right-click on the GPU and select "Update Driver Software..."
c. In the resulting window, choose "Browse my computer for driver software".
d. I navigated to the "C7..." file along the following path: <C:\ATI\Support\11-7_vista64_win7_64_dd\Packages\Drivers\Display\W76A_INF>
e. At this point, I was shown a window that showed "ATI Radeon HD 2600 PRO" twice (that's all that was in the list). I selected the first instance and it moved on.
f. I got a warning that the driver was unsigned, obviously I allowed it to move forward with the installation.
g. The updating proceeded and the screen momentarily went black, twice. After the second time the description in the Device Manager changed to reflect that the GPU was now "ATI Radeon HD 2600 PRO".
FINAL NOTE: as of right now everything seems to be running properly and I have experienced no problems or graphical glitches. If anyone reading this sees an obvious problem with what I've done, please let me know. I have run benchmarks between this and the standard installed mobility driver and I get about a 10% increase in overall FPS (using the free "NovaBench" app by NovaWave).
< Edited By Host >

look what this guy said:
Hi Guys,
I've spent a few hours over the last week trying to find something that works to update the driver. Using the Mobility Modder from Driverheaven I managed to install the Catalyst 7.8 but not the actual driver - you need to modify the INF for this. The only problem is that I can't be sure what the differences are between the mobility 2600 and the standard-computer 2600. I would like to assume it's just a few settings such as power saving and interal/ external displays.
I tried to modify the INF and used the settings for the standard graphics card. It worked fine, but I put the original Apple driver back on because I didn't want to find out I was overclocking the Graphics CPU accidentally.
After using mobility modder I added this line just after the mobility 2300 graphics card entry:
"ATI MOBILITY RADEON X2600 XT " = ati2mtag_RV630, PCI\VEN1002&DEV9583
If you notice and compare the mobility and standard entries, the mobilities have the same ati2mtag but followed by M-something rather than RV-something.
This appears to direct the INF to the correct setup of the Catalyst software for that card - as I say, I used the settings for the standard 2600 card and it installed ok. I didn't try any games though.
On another note, I'm resisting doing anything further or testing any games until I have the screen issue resolved - after exchanging the naff 20" screen with it's horizontal shading (a dark shade at the top to a light shade at the bottom - very noticeable with darkish solid colours!) I've found my new (more costly!) 24" is having some problems with picture breakup, though so far only in Vista which I installed via Bootcamp.
I wish Apple would get there act together. It's my first Apple and I was expecting great things! So far, I would have had less hassle if I had built my own computer with Vista on and thats saying something!!
Matt
he added the RV630 string. but i tried that with my exact windows xp driver device ids and yes it still completed the installation successfully,but the fps sill stayed the same

WinXP-64 bit corrupts existing RAID array

I've got an MSI K8N Neo2 Platinum motherboard running Win XP Pro SP2 on two 36 gig SATA Raptors. Everything was working fine, but I wanted to try the 64 bit version of XP. Grabbed an old 80 gig PATA drive and threw that in the case. Unplugged the SATA drives so as not to risk messing with the existing working OS. Installed the latest 1218 x64 beta and it worked well.
The problem was that when I shut down and reconnected my old RAID array, windows wouldn't boot from it. I lost everything and had to rebuild Windows from scratch. So now I know to never unplug the SATA drives
Rebuilt WinXP on the RAID array and then tried rebooting with the PATA drive with the 64 bit OS. Came up with the "drive needs checking" screen, and proceeds to "fix" the RAID array while ignoring my frantic pounding on the Logitech USB keyboard to stop. Rebooted and yes, the new install was nuked. Okay, since it's gone anyway, reboot to the 64 bit OS and make sure it's got the 64 bit RAID drivers installed.
Reinstall WinXP on the RAID array, reboot to the 64 bit OS on the other drive and the same old scandisk comes and nukes it AGAIN!
So now the PATA drive is sitting on the shelf again, unless someone here can suggest what is causing this problem.
System Specs
Athlon64 3500
gig of PQI 3200 at 2-2-2-5 2.6
2x36 gig Raptors on ports 3-4
Plextor PX-716a DVD+_RW
Visiontek X800 Pro.

The first time you re-installed Win 32 on the raid that was a bit drastic. A repair ought to have done the job.
The problem was probably that you disconnected the array but that's where the boot.ini was and that file needed to be modified to add the path to the Win64 install.
Since you took out the array the Win64 install created a new boot.ini on the PATA drive. Even when you tell BIOS to boot off the array, Windows has a bad habit of looking at the IDE channels & using the boot.ini if it finds one there - but the file it found didn't point to the array of course.
So basically if you already have Win32 on the array I would leave that array connected normally when installing Win64 on the PATA drive and all should be well.
I've installed Win64 on the same array as my Win32 install and they co-exist happily. I reckon that's the most efficient way to do it. The main thing is to make separate partitions for Win32, Win64 and data files when you install Win32 in the first place. The two OSs can share the same data files, incuding stuff like email.

Tutorial: Installing Windows XP 64-bit

After the fairly crappy time I had installing the 64 bit version of Win XP on my computer and peicing together various bits of information contained in various threads on this board in order to make it work, I've decided that I'm going to attempt to write as complete a tutorial as possible detailing the install process from beginning to end in hopes that it helps prevent people from running into the same problems I did. Anyways:
Step 1 - Acquire a copy of Windows XP 64-bit
Obviously you need a copy before you can install it, and you can get a free beta copy of Windows XP 64-bit Edition from here:
http://www.microsoft.com/windowsxp/64bit/downloads/upgrade.asp
You can either download the file (it's about 450 MB, though if you're on broadband your transfer will be over fairly quickly...microsoft.com servers always seem to offer excellent download speeds), or have physical CD's shipped to you. Either way it doesn't cost anything, all you have to do is fill out their form, and they'll give you your stuff.
Step 1a - Burn the .iso file to a CD
This section is probably wholly unnecessary, but for the sake of completeness, I'll include it...
If you had microsoft ship you a premade CD, skip this step. However, if you downloaded your copy of Win XP 64, you'll need to burn the image file you downloaded to a CD before you can use it. To do this, open your preferred burning software (I'd recommend using Nero), and select "Burn Image" (or the equivalent option for your software), and specify the .iso file you downloaded as the image file to burn. You should have your CD in a matter of minutes.
Make certain that you note and record the CD-key contained in the e-mail microsoft sent you. Writing this on the CD would be a good idea, as would printing out a copy of the e-mail.
NOTE: Do not burn the ISO file itself to a CD (i.e. create a new data CD and just drag the ISO file into the compilation window)...this will not work as it will put the file itself onto the disc, rather than the CD image contained within the ISO, which is what you want.
Step 2 - Prepare your system
Carefully preparing things before you attempt to install Windows XP 64 can save you a lot of headaches when install time actually comes.
First of all you want to make sure you have a seperate drive/partition to install Windows XP 64 onto (unless you're crazy enough to want a beta operating system to be your full-time OS...and I've seen Win XP 64 in action, and trust me, you do not want this just yet). If you are using RAID make sure you are using the VIA controller and not the Promise controller as from what I've heard there are no 64-bit drivers out yet for the Promise RAID controller. Also if you are using RAID, be sure to read the following thread, which details the process of putting the 64-bit RAID drivers onto a floppy disk, and follow the instructions carefully:
https://forum-en.msi.com/index.php?threadid=40859&sid=
Next, download all applicable drivers you can and save them in a sensible place (like c:\win64drivers). If the driver comes in an archive, be sure to pre-extract it as well (Win XP 64 does not come with native zip/rar support). It's okay if you don't want to get/cannot find all the drivers you'll need for your system, but at the very least make sure you download and extract the 64-bit ethernet adapter driver appropriate to your setup (most likely the RealTek RTL8169/8110 drivers), otherwise you'll be without internet (which makes downloading additional driver and program files kind of difficult). You may also want to pre-download the installation files for some of the more essential program, like Winzip and WinRAR. The best place I found to find 64-bit drivers is located here:
http://www.planetamd64.com/modules/mx_pafiledb/dload.php?sid=
Step 3 - Configure your BIOS
Certain BIOS settings can screw up the install process, causing it to lock up at certain points, so it's worth taking the time to make sure things are set properly.
Anyways, reboot your computer and go to the BIOS setup area, and make sure that "USB Legacy Support" is disabled, and that "Cool'n'Quiet" support is enabled...this will help reduce the chances of your installer hanging. I found that after my install had completed I was able to re-enable USB Legacy support and have everything still work fine, but your results may vary, and different BIOS versions may have different effects on the installer. I installed with BIOS version 1.20.
While you're here, check your Boot Order settings and make sure that your CD/DVD drive is listed before your HDD is, and then insert your Windows XP 64 CD into the drive. Save your settings and exit.
Step 4 - Installing Windows XP 64
When the computer reboots from step 3, you should see a message that says "Press any key to boot from CD..," so locate the "any" key and press it, and the windows installer will load.
If you've done everything mentioned in the above steps, your install process should hopefully be a painless one, free of the errors and random stupid crap that caused me to spend several hours doing something that shouldn't have taken more than 30 minutes. Select your desired install path (being careful to make sure that you're not installing over your 32-bit Windows) and enter information as requested. If you need access to your RAID array during the install process, then be sure to press F6 when it asks you, and load the driver off of the floppy disk you created.
If all goes well with the install Windows XP 64 should boot, and you can go and install all those handy driver files and software programs that you prepared in Step 2, and get your ethernet adapter working, and so on. Reboot your system after installing the updated drivers, and if windows successfully loads, then congratulations, your install was successful.
NOTE: Do not install the MSI LiveUpdate software from the CD, as I did this and when Windwos loaded I would get a message saying "The service is not started" and when I clicked "Ok" the system would spontaneously reboot. Disabling the software fixed this problem.
...I think that's all. Let me know if I've missed anything.

Quote
Originally posted by Some1ne
Here's a step-by-step description of how to install the RealTek RTL8169/8110 driver, as the process isn't quite as straightforward as it should be:
1. Download the Windows AMD64 Drivers available here:
http://www.realtek.com.tw/downloads/downloads1-3.aspx?series=16&Software=True
2. Extract the files in the archive to somewhere like c:\win64drivers\ethernet
3. Once inside Win XP 64, do the following:
a. Click Start -> Settings -> Control Panel -> System -> Hardware -> Device Manager
b. Go down to the "Other Devices" section (they'll have yellow ?'s)
c. Right click on the ethernet controller and click "Update Driver"
d. Click "Install from a list or specific location (Advanced)"
e. Click "Dont search. I will choose the driver to install."
f. Double click the "Network Adapter" entry, and then click "Have Disk..."
g. Select the directory which you extracted the driver files to
i. You will get messages saying that Windows cannot verify that the driver matches your hardware, and that the driver is not WHQL certified. Ignore these and click "Continue"/"Install Anyways" and your RealTek RTL8169/8110 ethernet adapter will spring to life
after i have done this the pc just stops. and if i reboot it stops at the loading screen :/ can you tell me whats wrong i got a k8t neo serie card and windows 64 bit edition
edit: i did it :D works now

Issue with 64 bit MS Office and Conversion to OPM 10.4

Just updated to OPM 10.4 and tried opening an existing project. It seemed to convert fine, but when I tried to open the Word file, and it opens Visual Basic with the following error:
Compile error
The code in this project must be updated for use on 64-bit systems. Please review and update Declare statements and then mark them with the PtrSafe attribute.
I am not a programmer, so I have no idea what this means. Any suggestions?
Thanks!

Hi Kristen,
I’m guessing this is specific to Microsoft Office 2010 64-bit. I’ve been using Microsoft Office 2007 32-bit with OPA 10.4 and I haven’t seen anything like this. I don't know the cause here, but just wanted to collect some more information which I'm antipating the product team may want to know...
- Operating system of your machine? (I'm assuming Windows 7?)
- What happens if you try to compile the rule doc from OPM rather than from within the Word doc itelf (right-click on the rule doc in OPM, select 'Compile' from the context menu)? Does it compile okay? If not, what happens?
- What happens if you create a brand new project in OPM 10.4? Does it work? Or do you get errors when opening the Word docs?
Cheers,
Jasmine

Okay since last apple software update my safari will not open youtube,yahoo or google

Okay since last apple software update my safari will not open youtube,yahoo or google, an error message comes up saying safari cannot connect to the server. Can anyone help me with this please?

Hi Joshua ..
Check to see if Safari is running in 32 bit mode. Right or control click the Safari icon in your Applications folder then click Get Info. If the box next to: Open in 32 bit mode is selected, deselect, quit then relaunch Safari to test.
If that wasn't the issue, try using OpenDNS.
Use OpenDNS for better speed, more security, prevents the, "can't connect to server" issue, includes anti phishing filters, prevents browser re directs, and it's free.
Open System Preferences / Preferences then select the Network tab. Click the Advanced tab then click the DNS tab.
Click +
Enter these addresses exactly as you see them here.
208.67.222.222
Click +
208.67.220.220
Then click OK.
More about OpenDNS here.
Topic : Manually provided DNS server addresses are higher priority than DHCP's

Cannot Install itunes 9.1.1.12 on Windows 7 64-bit

I keep getting the same error whenever I try to install iTunes: +This iTunes installer is intended for a 32-bit version of Windows. Please download and install the 64-bit iTunes install instead.+
According to this link: http://support.apple.com/kb/DL1037, it is the 64-bit installation software.
So I tried this as suggested by Microsoft: +Use the Windows Installer Cleanup Tool and see if it helps. Click here to download. Then try to install the most current version of iTunes.+
I did that...but nothing.
So I tried this suggestion...+Right click your mouse, next you will see a drop down menu and in the middle you will see "Install as Administrator" Left click on that option and let the install begin.+
That didn't help either. I got the same error message of the 32-bit thing.
Each time I try to install, I make sure all Apple sofware has been removed from my computer, even any iTunes files in my Music Folder, etc. Then I reboot. I even cleared all of my internet caches.
I'm not sure what else to do. This is a new computer, we got it about four days ago.

Okay, the bookkeeper's office has firefox, so husband downloaded it using his computer. But once I tried to install on my home computer, I got the same 32-bit message. Something you mentioned did catch my attention: iTunes64setup.exe
This is what the properties read on the installer:
File Version: 9.1.1.12
Original File Name: iTunessetup.exe
Is this where the problem is? Should it say iTunes64setup.exe?
He has been clicking on 64-bit link. But it seems to not be downloading an iTunes64setup.exe file, but is instead downloading iTunessetup.exe. Does this have to do with his work computer not being 64-bit? Do you have to download from a 64-bit computer?
Again, thanks for responding. I really appreciate it.

AFP authentication a bit too forgiving?

Having been reasonably satisfied with the performance of Leopard on my 24" iMac, I decided it was finally time to upgrade the rest of our office machines as well. It was only after I bought a recent Mini that I realized file sharing in Leopard features a new behavior that I find less than acceptable.
This is the problem I discovered: when I use AFP on one Leopard machine to access a shared folder on a remote Leopard machine, the login information persists even after I unmount the shared folder. Using the same local machine I can connect to the remote machine again and again without ever having to re-enter a password. This came as a bit of a surprise, since I was used to the Tiger way of doing things.
http://www.radiotope.com/content/more-about-os-x-105-leopard-kerberos
After a modicum of googling I came across the above blog entry, which explained this behavior to me. It appears that I've been kerberized, and this persistence of login information is in fact intended as a convenience. And there I was, thinking it was a *big ol' security hole*. Silly me!
I don't think I can be blamed for my misapprehension. I can think of a number of ways this setup can be exploited for all sorts of nastiness. Let's take the first one that comes to mind:
I admin several Macs for our small business, and I'd rather not clog our struggling DSL line by using Software Update to download updates individually for each machine. So I log into the admin account on my iMac, manually download all the updates we need, and file them in an appropriate folder. Then I walk over to my wife's Mini (assuming I can find a few minutes when she's not using it), log into my admin account on that machine, use AFP to connect to the admin account on my iMac, copy over the download files, and unmount the folder. So far so good; were this Tiger, it would be the end of the story.
But in Leopard, we're just getting started.
As I've already explained, if I try to connect to the iMac again, I'm allowed to do so without typing in a password. This is a bit surprising, but I can see where some might find it convenient.
I find I can also log out of the admin account on the Mini, log back in, and still connect to the iMac without typing in a password. Okay, we've gone from "surprising" to "unsettling."
But that's nothing. I can also log out of the admin account on the Mini, log into my wife's normal user account, and still connect to the iMac without typing a password! ... Which means that if I log out of the admin account and walk away from the Mini, my wife will be able to log into her account +and gain instant, unrestricted access to any file in the admin account on my iMac.+
Hmmm, I've just gone all the way from "unsettling" to "major heebie-jeebies."
This probably isn't much of a problem in a small family business like ours. My wife knows there are good reasons why I don't want her messing around with the admin accounts on our computers (not least of which is the danger of extended computer downtime), and I trust her to keep her mitts off them. But I still keep the admin account passwords to myself because I don't want her accidentally screwing something up. Leopard has given her a way around this failsafe: it's made it possible for her to unintentionally mess up the admin account on my computer!
In a large company, it could be a much bigger problem, made all the worse because the user gets no warning that the login info will persist after he logs out. Rewrite the above scenario, but replace me with a harried system admin who's new to Leopard and isn't aware of this "convenience," and in my wife's place imagine an unscrupulous employee who suddenly finds he has access to all the files in the admin's computer. What fun he (or she) could have!
This has gotten quite lengthy, but I don't think it makes sense to be word-stingy when a big stinkin' security hole is apparently being passed off as a convenience. I hope I've managed to get my point across.
That being said, I'd like to ask a question:
Is there some way to turn this functionality off so that users will be required to log in every time they try to access files via AFP? I'd rather do things the old way, if possible. (I know it's possible to use the Kerberos app to burn the ticket, as the blog author suggested. But there's always the chance that I'll forget; and even if I don't, it's a pain in the posterior.)
Also, a suggestion:
Wouldn't it be a good idea to rethink this functionality? It seems to me that at the very least, Leopard should display a warning anytime someone tries to connect to a remote machine via AFP:
*+Warning! For the next ten hours, anyone who uses this machine will have unrestricted access to the account you're about to log into. Are you sure you really want to go through with this?+*
But such a warning would beg the question: Why does this function even exist? Perhaps it would be better if the functionality were turned OFF by default...

Thanks for responding, Scott.
Yes, what you describe is exactly what happened. I wouldn't have written what I did without trying it first.
That said, I tried it again after reading your post, and it isn't happening now. In the meantime I've rebooted both of the computers in question and tinkered with a few settings, so it may be that the remote Mac was in a strange state that I've somehow jarred it out of. Or maybe I was just seeing things. In either case, I appreciate your taking the time to clarify the issue, and I'll allow myself to breathe a tentative sigh of relief -- on the assumption it'll keep working the way it is now.
On a more theoretical level ...
Although I understand that connection credentials are intended to persist, I'm not entirely convinced that there's nothing wrong with this. The blog I linked in my original post cites an example of how this arrangement can lead a user to inadvertently grant another user access to files on a remote machine.
Let's say my wife needs a file that I know I have in my admin account on my iMac. Rather than walk all the way over to my desk and put the file in her dropbox, I get her to scoot over, log into the iMac remotely, and drag the file onto her desktop. Then I unmount the iMac and let her get back to work. Presto! I've just given her access to my admin account (and indeed the whole iMac) for 10 hours.
I know, I know, this is really an example of bad computing practice. However, it's the sort of thing folks do every day without thinking about it. Still, we can say this in Leopard's defense: it's up to the user to know how the system works, and to avoid doing things that lead to undesired results.
What makes it a problem is the fact that Leopard is doing something, by default, that its predecessors did not do. And it does so without alerting the user to the fact that things are being done differently. Someone used to the pre-Leopard way of doing things is all too likely to disconnect from a remote computer and walk away, thinking that the remote account is still password protected.
All this makes it possible for a new Leopard user to give another user access to sensitive or valuable data +and remain completely unaware that he has done so.+ Even if that is not as bad as the "second account" scenario I described in my original post, it still strikes me as a bit of a security risk.
I'd be happier if credential persistence were turned off by default. Or if there's a way to turn it off, I'd sure like to know about it.

Is 32-bit okay?

Similar Messages

Maybe you are looking for