Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

Xaero_Vincent Xaero_​Vincent Sexy me
  • Seamless Windows Terminal Server for Linux

    Update #1: Greatly improved the "Readme" document.

    Update #2: Re-built RPMs against latest CVS repository.

    This update fixes a potential connection issue with Windows Vista SP1 terminal servers and changes a datatype that could cause issues on non-x86 architectures.

    Update #3: Added a note in the readme that clarifies when to click the SeamlessRDP shortcut and re-worded a few other paragraphs. The notice is only applicable to Vista terminal servers.

    Update #4: Added some Windows XP-specific notes in the readme document.

    Update #5: Re-built RPMs against the latest CVS repository, added Greek keymap, and enabled support for smartcards.

    Download update here.

  • Another nail in the .NET coffin

    DigitalDud wrote:
    It's nice to see the Linux guys catching up with what Windows and Mac development environments have had for 15 years.


    Since when was QT a Linux-only API? Notice how its for Windows and OS X too.

    Probably the biggest problem with Linux and FOSS UNIXs is that they have nothing to claim for themselves.

    That is the side-effect of being both free, open source and having the least marketshare.

  • ATI catalyst 8.1 - introducing multiwhat?

    SlackmasterK wrote:
    


    I bet all those monitors are EnergyStar compliant too, right? Wink

    Oh and the two other pieces of interest... two Cheez-It boxes? :O

  • Seamless Windows Terminal Server for Linux

    XP or older version users:

    If you cannot log off the terminal server because the taskbar and start menu is missing, create a shortcut on Linux and add this target command:

    rdesktop -l "logoff"

    This will launch the logoff.exe in Windows, which will log you off.

    Just click the shortcut whenever you want to log off.


    If you want a taskbar to appear create a shortcut with this:

    rdesktop -l "explorer"

  • Seamless Windows Terminal Server for Linux

    <clean>

  • Seamless Windows Terminal Server for Linux

    <clean>

  • Seamless Windows Terminal Server for Linux

    <clean>

  • Seamless Windows Terminal Server for Linux

    Here is an early Christmas gift to our fellow niners with Windows and Linux boxes, who are looking for an easy way to access their Windows applications and remote files when Wine-type solutions fall flat.

    I've packaged together a set of software components that provides a seamless terminal solution to Fedora Linux users with access to capable Windows machines or virtual machines on the local system.

    "Seamless" refers to the interaction of individual programs in their own, seperate windows and launching them from shortcut icons on the Linux desktop. This is contrast to a normal remote desktop sessions, where the full desktop is presented in a single window.

    I've made RPMs for an enhanced, patched CVS version of rdesktop (RDP client), included Microsoft's Elevate Power Toy for Vista, Fontis IT's enhanced SeamlessRDP server and my small tray application and readme.

    Be sure to check the Readme file.


    Requirements
    ==========

    * Access to a computer with a version of Windows that encompasses the server component of terminal services: Windows NT 4.0 TS, Windows 2000, Windows XP Professional, Windows Server 2003, Windows Vista Buisness, Ultimate, and Enterprise. Windows Server 2008 terminal servers are currently not supported.

    (Note): If local or remote access to a Windows machine is not possible, a virtual machine with host networking configured and a Windows guest operating system can be used in place of a physical system. The seamless terminal server should function the same in a virtualized environment. This document does not describe how to configure a virtual machine.

    * At least one computer installed with Fedora Linux. Although this software is capable of running on numerous distributions and other Unix-like operating systems this particular package has only been tested with 32-bit versions of Fedora and Windows. Users of other distributions and operating systems may attempt to covert the RPM packages to the native package format of their distribution or operating system with tools like Alien.

    (Note): Re-compiling the SRPM and SeamlessRDP components are necessary for 64-bit machines with 64-bit operating systems.

    * Any sort of network or Internet connection for both the server and client. A simple 56K modem connection would be sufficient. Be aware that internal dial-up Winmodem support under Linux is poor at best; therefore, for most users, options are limited to a hardware modem, wired Ethernet or wireless connectivity. The terminal server system may be accessed from a local or wide area network or via the Internet.

    Enjoy.


    Update: Download from the 4shared link instead. It appears I reached my upload limit for this contribution on here. Perplexed

    http://www.4shared.com/file/35396677/f60a9ae4/sts.html

  • Vista SP1 - My Windows is now an ​"​Evaluation Copy' WTF

    I cannot wait for SP1.

    Faster local and remote file copy operations is something I've long needed from from Vista. Its presently slower than a turtle climbing a steep grade.

    The new RDP compression algorithm sounds sweet too... upto 50% less bandwidth requirements? That will be totally swell for my Terminal Server.

  • Why doesn't Microsoft buy SCO?

    evildictaitor wrote:
    And that's why Linux doesn't have a big market-share, right there.

    If Linux developers started to realise that actually users having a good experience is much more important than silly long-term grudges they might hold, or stop bickering about whether Linux ought to even allow programs not released under the GPL, they might actually get some users.

    They should get their act together and put in a single line at the top of their kernel:

    if(VPC) then { don't use 24-bit color }


    And until they do, normal users who just want their computer to work and who might want to try out that new and fangled "Linux thing" will be absolutely sure to not touch it if it doesn't just work.


    The only way this would be true is if the Xorg drivers for whatever video card Virtual PC virtualizes only supported up to 24 bit video mode.

    That is a possible scenerio but it doesn't mean that Xorg fails to support 32 bits per pixel for other cards and drivers.

    > grep -G pixmap /var/log/Xorg.0.log

    (==) Depth 24 pixmap format is 32 bpp

    > xdpyinfo | grep '32'

    bitmap unit, bit order, padding:    32, LSBFirst, 32
        depth 1, bits_per_pixel 1, scanline_pad 32
        depth 4, bits_per_pixel 8, scanline_pad 32
        depth 8, bits_per_pixel 8, scanline_pad 32
        depth 15, bits_per_pixel 16, scanline_pad 32
        depth 16, bits_per_pixel 16, scanline_pad 32
        depth 24, bits_per_pixel 32, scanline_pad 32
        depth 32, bits_per_pixel 32, scanline_pad 32
      depths (7):    24, 1, 4, 8, 15, 16, 32
        visual id:    0x32
        depth:    32 planes

    > info xorg.conf | grep -B 10 -C 4 "Most hardware"

           Depth  depth
                  This entry specifies what colour depth the Display subsection is
                  to  be used for.  This entry is usually specified, but it may be
                  omitted to create a match-all Display subsection or when wishing
                  to  match  only against the FbBpp parameter.  The range of depth
                  values that are allowed depends on  the  driver.   Most  drivers
                  support  8,  15,  16  and 24.  Some also support 1 and/or 4, and
                  some may support other values (like 30).  Note: depth means  the
                  number  of  bits  in a pixel that are actually used to determine
                  the pixel colour.  32 is not a valid depth value.  Most hardware
                  that  uses  32  bits  per pixel only uses 24 of them to hold the
                  colour information, which means that the colour depth is 24, not
                  32.