Has anyone tried kdb on win10?

Community Support
1

as title. thx

2

Yes it does work.   I spun Q up on Windows 10 VM under OS X + Parallels just now to check for you. 

btw: for consistency with Linux, I prefer to install under %UserProfile%\q.  Here that translates to c:\users\steven\q

Don’t forget to set the environment variable QHOME if you go for the %UserProfile%\q option (rather than c:\q).  This command for Win 7 / Win 8 / Win 10 might help with that:

    setx QHOME %UserProfile%\q

Start q by executing q\w32\q.exe.  

You might want to add that to your path statement, or alternatively, here’s an ugly trick for creating aliases under Windows.

Use 

   @doskey q32=%UserProfile%/Q/w32/q $*

 

   or 

   @doskey q=%UserProfile%/Q/w32/q $*

cheers,

-Steven T.

3

although that alias trick will works fine, probably the better way to fake an alias under windows is to create a batch file and use the %* wildcard to pass on arguments when you use them.

   @%userprofile%\q\w32\q.exe %*

The reason I mention that is that my windows equivalent to .bashrc stopped working under windows 10.  

-Steven T.

4

Q install went fine, however when I try:
setx PATH “%PATH%;C:\q\w32”

I get:

WARNING: The data being saved is truncated to 1024 characters.

SUCCESS: The specified value was saved


so it was not added to my PATH, since it was too long.

Any suggestion on another way to do so?

5

Shorten your PATH? Not sure what exactly this has to do with kdb *or* win10…On Wednesday, November 29, 2017 9:31:36 AM CST, Brian Colgan wrote:> Q install went fine, however when I try:> setx PATH “%PATH%;C:\q\w32”>> I get:> WARNING: The data being saved is truncated to 1024 characters.> SUCCESS: The specified value was saved>> so it was not added to my PATH, since it was too long.> Any suggestion on another way to do so?-- Ryan (???)Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone elsehttps://refi64.com/

6

Hi Brian,

I encountered a similar issue on Win10, this is how I got it working:

  1. Open up Explorer
  2. Right-click on My Computer and select Properties
  3. On the left, click on Advanced System Settings
  4. Click on Environment Variables
  5. In the top of the two windows, scroll down to Path (or PATH)
  6. Click Edit
  7. Click New in the window that pops up
  8. Add C:\q\w32
  9. Click OK, OK and OK
  10. Restart the command line and check if q works now.

Collin

7

it’s a bug with setx that’s been around for a while. Paths can be longer than 1024 characters. The GUI approach by Collin is a good fallback. If you need a script based way forward, here are a few references for you:

https://superuser.com/questions/387619/overcoming-the-1024-character-limit-with-setx

https://superuser.com/questions/297947/is-there-a-convenient-way-to-edit-path-in-windows-7/655712#655712

https://stackoverflow.com/questions/17240725/setx-doesnt-append-path-to-system-path-variable