NIM

Do you have admin permissions? No matter it lists only x64 drivers, you should be able to add the x86 driver.

Click ALT on the keyboard, it should show you the Explorer Menu.

Don't do that, don't click on the printer. Just open the share and mark the printer, then go to File | Server Properties, then from the Driver Tab add the x86 drivers that you downloaded, and they will then be uploaded to the server ....

Welcome, hopefully you'll be an active member in this community

Ok, try to add a new printer using IP address (just like you're installing the network printer on the server), only you can. When you're asked to provide a driver, provide the path to your x86 printer driver. Using this steps, you should be able to install the printer, but you won't be using the print queue of the server, but rather on your x86 PC. I hope this is not a problem to you. If yes, I'll try to dig another solution for you.

By latest reviews I've found out that Revo Uninstaller is one of the best tools for the job.

Sometime ago I wrote an article about this on our frontpage, so here it is: To get the x86 drivers to work with the x64 Windows 2008 Server you will have to connect to the server from the 32-bit (x86) client and open the printer and faxes share. From the File Menu select Server Properties, then from the Driver Tab add the x86 drivers that you downloaded, and they will then be uploaded to the server. What you should know is that both x86 and x64 drivers MUST have the same name. If they have the same name, they will automatically appear as additional drivers for both architectures in your printer’s sharing properties. On Windows Server 2003 x64, some x86 print drivers are not installable directly at the server console. However, you can browse the network from the x86 machine to \\servername\printers and faxes, open server properties, and add the x86 driver from there. One more issue that you might experience on Windows Server 2008 is an error about the printer driver not matching, where the system is looking for the file NTPRINT.INF. You can get a copy of this file from the Windows 2008 Server x86 CD or from a downloaded x86 driver. Here is the step by step procedure: Access the x64 print server \\PrintserverName\Printers from a x86 Cllient. Open the printer required to add the 32-bit driver. Properties | Sharing Tab | Additional Drivers Check the x86 for Windows 2000, Windows XP and Windows 2003 checkboxes. Click OK. System will ask you for NTPRINT.INF drivers. Locate the INF file of the print driver for XP (x86) which resides on the Windows Server 2008 CD or in extracted print driver downloaded from the net. Locate the INF file of the printer driver for XP 32-bit. That should be it. If you experience any issues please post your comment below and I will try to help. http://www.wincert.n...bit-or-x64.html Hopefully it'll help

Which card did you get Reaper?

Happy Birthday Lego, and thanks for your kind contribution to this forums! All the best!

bphlpt is right, unfortunately this bug still hasn't been fixed. Please refer to this topic: Also, here's the official reply from IPB regarding this bug: I will disable the lightbox for now, so at least we can avoid this issue.

If you would like to setup up synchronization between two folders (local or network), but you're not sure on how to do this, this is the right tutorial for you. For this purpose I will setup a folder synchronization of my local folder with my network folder on Popcorn Hour device. I am using Windows 7 x64 and for the synchronization I will use Microsoft's SyncToy 2.1 Synctoy is a free application and can be downloaded from Microsoft Web site on THIS link. If you find provided link invalid, please Google for Synctoy and download the appropriate installation package (x86 or x64 version) Once you install the Synctoy you'll find it very easy to set up the synch. Run the SycToy and click on the 'Create New Folder Pair' button Select 'Left (source)' and 'Right (destination)' folders by clicking on the Browse buttons I have selected F:\_System Tools as the Left folder and Z:\_System Tools as the Right folder. (Popcorn network drive is mapped under Z: letter) On the next screen choose one of the desired options: Synchronize; Echo or Contribute (check each of this settings in Short Explanation Box on the right). This can also be changed later on. For this purpose I will use Synchronize option Now, you should only name your folder pair. For instance System Tools Synch On the main screen click RUN to run folder synchronization on the pair you've created As you can see, my two folders were synchronized without errors. If you receive errors, you might want to check for write permissions on both folders. Ok, now we can setup a scheduled task in Task Scheduler, so this synch can run automatically. Hit Win ORB and type Task Scheduler | on the Start Menu click on the Task Scheduler. Click on the Action | Create Basic Task | Name: System Tools Synch | Trigger: Choose when the task should start | Action: Start a program | Browse for the SynctoyCmd.exe (default path is "C:\Program Files\SyncToy 2.1\") | Under Add arguments type -R to run synchronization of all folder pairs configured in Synctoy | Under Start in please copy/paste the path to SyncToy folder: "C:\Program Files\SyncToy 2.1\" Note: If the folder pair name contains a space, surround it with quotation marks as in the picture below for the Program/Script window, but REMOVE the quotation marks in Start in box or your task won't work. Click Finish twice. In the Task Scheduler, on the left pane highlight Task Scheduler Library and in the right pane mark System Tools Synch. Right click on the scheduled task that we've just created and click Run For some reason I've received an error 0x8007010B error and I've discovered that quotation marks has to bee removed in the Start in box. After that change, my scheduled task was run without errors. If you experience issues, please post below. Update: One of our users reported that he receives the following error when trying to run the scheduled task: SCHED_E_TASK_ATTEMPTED 0x80041324 The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition. Solution: The problem was in the Conditions tab of the scheduled task where he had enabled setting 'Start the task only if the computer is on AC power' and his laptop was on the battery power. Either plug-in the laptop or remove disable that setting in the Conditions tab.

If you have the corporate policy to use only given screesaver, here's how to do it on Windows 7 Professional, Enterprise or Ultimate edition. Hit Win ORB and type gpedit.msc to start up Group Policy editor In the left pane of Group Policy editor navigate to: User Configuration | Administrative Templates | Control Panel | Personalization Now, in the right pane double click on the 'Prevent changing screensaver setting' and select 'Enabled' Close Group Policy editor You're done, it was fairly simple right Comments are welcome!

You may experience the following error message when trying to run a Scheduled Task. SCHED_E_TASK_ATTEMPTED 0x80041324 The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition. The cause of this issue is in the Conditions tab of the Scheduled Task Properties. For instance, you're using your laptop on the battery power to run the task, but the Conditions tab has 'Start the task only if the computer is on AC power' enabled. This way you won't be able to start the task. Either plug-in the laptop or clear the checkbox on that option.

I am using Aero Peek very often to navigate through open applications/explorer items in the taskbar. If you use it too, you have probably already noticed that thumbs open rather slow when you hover over the taskbar application. Luckily there's a way to speed this up so the thumbnail opens instantly as soon as you hover over any open application in the taskbar. Here's how to do it: Hit Win ORB | Type REGEDIT | Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced In the right pane right click on on the white area and create a New DWORD (32-bit) Value (if you're using Windows 64-bit, if not mind the (32-bit). Type ExtendedUIHoverTime and click OK | Double click on the ExtendedUIHoverTime key and in the Value data box type 1 | click OK Close the registry editor and restart your machine for changes to take effect. Notice that thumbnails opens instantly as you hover over the application shortcut in the taskbar. If you would like to revert changes we made now, just change the Value of the ExtendedUIHoverTime key in the registry to 0. OR just delete the ExtendedUIHoverTime key. On the other hand, if you would like to slow it up, you can use a custom value like 2000 or 3000 in the Value box. Comments are welcome!

If you find taskbar thumbnails annoying, there's an easy way on how to get rid of this feature. Have in mind that there are a lot of suggestions on the net on how to achieve this, but none of that work, at least not on mine Windows 7 x64 Ultimate system. This suggestions include editing local security policy, editing registry and using keys like 'TaskbarNoThumbnail' (that is created if local security policy is edited), DisablePreviewWindow and so on. None of this works. Below solution won't disable the taskbar thumbnails, but rather will extend the delay of it. To disable the taskbar thumbnails in Windows 7 please do the following: Hit Win ORB | Type REGEDIT | Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced In the right pane right click on on the white area and create a New DWORD (32-bit) Value (if you're using Windows 64-bit, if not mind the (32-bit). Type ExtendedUIHoverTime and click OK | Double click on the ExtendedUIHoverTime key and in the Value data box type20000| click OK (This will extend the thumbnail hover time to 20 seconds). Close the registry editor and restart your machine for changes to take effect. Notice that there's no thumbnail appearing when you hover over the taskbar items. If you would like to revert changes we made now, just change the Value of the ExtendedUIHoverTime key in the registry to 0. OR just delete the ExtendedUIHoverTime key.

Forum upgraded to latest version. This was a minor update. As I can see, linking problems reported in this topic are still present. Time to report again. Update info: Between 3.2.0 and 3.2.1 the following changes have been made: A setting has been added to restore the ability to have proportionate profile photo sizes in topic view (3.2.0 enforced cropped square thumbnails). The visual skin editor has been enhanced to support more areas of the board. Several enhancements have been made to the webDav integration for external skin editing. More than 170 bug fixes have been implemented to IP.Board 3.2.0.

If someone would fill it with useful posts, I'd gladly create it.

As already said, go for one stronger card, rather than two in Crossfire mode (if that's still the name I know that I once read that second card in Crossfire mode only gives like 30% of it's performance, but can't be sure what's the case now in the means of 2 card performance.

You can safely remove those files, but if you want you can leave them also. You won't have any issues.

I've read somewhere that Machinarium 2 is in the development

Rick, that new monitor has these lines or this is a laptop?

For now, the solution is to right click on the button/link and then open the link in the new tab/window. This will be fixed in the upcoming release of the forum software.

My first build was on Pentium 2 @ 400mhz and 128mb of ram, along with the 13,5gb hard drive. I also had matrox millenium g400, if I remember correctly. I know I borrowed money for this beast