avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Friday October 30, 2020, 8:33 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ewemoa [ switch to compact view ]

Pages: prev1 ... 108 109 110 111 112 [113]
Thanks for the consideration :)

I hope you have success in the process and that it doesn't take much of your time or resources!

General Software Discussion / Re: Critical vulnerability in Windows
« on: October 23, 2008, 11:45 PM »
Thanks for the heads up  :)

FWIW, I've applied the update on 3 machines and so far haven't encountered any obvious problems.

Not sure if this counts as the same/similar kind of situation, but in v2.30.01, after I bring up FARR and type:

+cmd c:\p

and follow this with the press of the tab key, the text in the search edit box becomes:

C:\Program Files\

Note that the alias "+cmd" has disappeared...Is this the way it is supposed to work?

[1] In my local installation, cmd is a an alias for:

Command Prompt Here | cmd.exe /k cd /d "$$1"

FWIW, I tried to duplicate this after a fresh install [1] of 2.30.01 under Windows XP Pro SP3 and the result was that I only got one entry in my Startup folder.

[1] I didn't run FindAndRunRobotInstall.exe to install -- I just unzip and run FindAndRunRobot.exe from within the resulting folder.

Launching something that uses an alias via a numpad key leaves "residue" in the Search Edit Box for my local installation.

Below is a description of how one might reproduce.

0. Fresh install of FARR v2.30.01 (I used VirtualBox for this).

1. Create a shortcut to "C:\Program Files" on the Desktop (if the shortcut isn't named "Program Files" already, please rename it to match).

2. Configure a way of toggling FARR that doesn't involve setting or clearing the previous search text:


3. Create an alias 'cmd' for opening cmd.exe with a search result (as described in: https://www.donation....msg120331#msg120331):


4. Bring up FARR using the toggling method defined in 2. and type:

+cmd program f


5. Launch the "Program Files.lnk" result via the appropriate numpad key (let's say for the sake of discussion that it was the first result, so press 1 on the numpad).

6. Bring up FARR again (using the method defined in 2.). 

What I get for the content of the Search Edit Box is (note the trailing number):

+cmd program f1


What I expect is no "residue" (trailing number):

+cmd program f

FWIW, I see the number appearing in the Search Edit Box after I press the numpad key and before the FARR window disappears -- sorry, my visual processing was fast enough, but my fingers were too slow to get a screenshot  :-[

I didn't match the above description to anything listed in 'FARR v2 - Official Bug Tracking and Feature Request Thread' nor did I succeed in locating a post with a closely matching description (perhaps my bad).  I did find a couple of other topics where similar-sounding situations were discussed - but I didn't come away with a confident sense of whether the associated descriptions dereferenced to the same phenomena  ;)


General Software Discussion / Re: Firefox 3.1
« on: October 18, 2008, 06:01 PM »
Thanks for the summary!  :Thmbsup:

P.S. Thanks for Tech News Weekly too -- very much appreciated!

so VDK is the windows analog of *u*x /dev/loop , basically?

They do seem fairly similar.

I've been testing out ImDisk (not VDK) recently, and I'm definitely reminded of loop devices. 

FWIW, I noticed the following under 'Warnings and Limitations' on the aforementioned VDK page:

VDK does not communicate with Windows 2000/XP Mount Manager.

Disk Management Console (partition manipulation and mount point configuration) does not recognize the VDK virtual drives.
Many third party utilities, such as PartitionMagic, work fine.
Disk Defragment utility does not recognize the VDK virtual drives.
Many third party defrag utilities, such as Diskeeper, work fine.
Graphical mode of Check Disk may not work.
(command line chkdsk.exe works fine).

Perhaps eventually there will be out-of-the-box / more-integrated-with-OS support for something like VHD in a future version of Windows, but in the mean time, at least ImDisk is coming in handy for me ;)

A shot in the dark may be, but...I noticed the following pieces of text on a page on VDK:

VDK can also open the following types of virtual disks:

Raw sector image which you can create with regular disk dump tools such as Linux dd command.
Non-partitioned disk image, such as floppy image, removable disk image, and dd image of a single partition. (This is not actually a type of virtual disk, but rather how the virtual disk is formatted.)
In this case, the whole image is treated as a single partition.

VDK is a disk driver, not a file system driver, therefore you can only access partitions which your Windows host can recognize. For example, you cannot access ext2 partitions on virtual drives unless you have a 3rd party ext2 file system driver installed on your Windows system.

So perhaps something useful can come about using VDK (or may be ImDisk) along with 'Ext2 Installable File System For Windows' / ext2fsd...

Clipboard Help+Spell / Re: Problem with Internatinal codepage
« on: October 14, 2008, 08:06 AM »
FWIW, I experienced similar difficulties with CJK text when trying out CH+S (v1.19.02) -- perhaps it's the same issue. 

I hope to try it out again once a newer version is released  :)

Pages: prev1 ... 108 109 110 111 112 [113]