x64 Support

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Sep 21, 2008
9
0
#1
Hi, I poked around a bit on the new forum here, and didn't see too much about x64 support. On the old Sparklist forum Rex Conn jumped in and mentioned there was not much to be gained by an x64 version, but that it was being worked on. However, I have recently run in to some issues, that has brought me back here. When using 4NT 7.01.370, if I try and run some 64bit console apps I get errors with the software or even "file not found". The most recent problem was when I tried to run "sfc /scannow". I get this message: Windows Resource Protection could not start the repair service. If I run it from cmd.exe, it works fine. I have noticed when doing a directory listing some files won't show up with 4nt.exe, but I can see them in explorer or a cmd.exe prompt. Any ideas what might be wrong?

Thanks,
j

P.S. Wow.... going on twenty years using 4DOS and its descendants! I can't think of too many other software products with that kind of staying power.
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,376
39
Albuquerque, NM
prospero.unm.edu
#4
That's the cool thing. You can download and it and try it out - for free - before deciding whether you want to spend the money. (Unfortunately I know nothing about x64, although I vaguely recall that there were some minor x64-related changes in one of the updates.)
 
Sep 21, 2008
9
0
#5
That's the cool thing. You can download and it and try it out - for free - before deciding whether you want to spend the money. (Unfortunately I know nothing about x64, although I vaguely recall that there were some minor x64-related changes in one of the updates.)
Good call, but unfortunately the issues still exist:

[C:\Program Files (x86)\JPSoft\TCMD9]sfc /scannow

Windows Resource Protection could not start the repair service.

[C:\Program Files (x86)\JPSoft\TCMD9]

-j
 
Sep 21, 2008
9
0
#6
Ok here is an even better example. Open up a cmd.exe prompt and cd to your windows\system32 folder. Type "dir >cmd.txt". Obviously this pipes the listing to the text the file. Now here is the catch. Open up a TC window and navigate there. Try to find the file. Here is my result:

C:\Windows\System32]dir cmd.txt

Volume in drive C is unlabeled Serial number is 6a1b:c464
TCC: (Sys) The system cannot find the file specified.
"C:\Windows\System32\cmd.txt"
0 bytes in 0 files and 0 dirs
68,354,109,440 bytes free

-j
 
Sep 21, 2008
9
0
#7
Ok..... Windows is pulling some kind of snow job on me. If you replicate the the previous example with TC:

Code:
TCC  9.02.152   Windows Vista [Version 6.0.6001]
Copyright 2008  Rex Conn & JP Software Inc.  All Rights Reserved
Your evaluation period expires in 30 days.
You can order Take Command at http://jpsoft.com

[C:\Program Files (x86)\JPSoft\TCMD9]cd \Windows\System32

[C:\Windows\System32]dir >tc.txt
tc.txt actually ends up in a folder called "C:\Windows\SysWOW64" if you try and find it with a 64bit program. I need an aspirin.

-j
 

rconn

Administrator
Staff member
May 14, 2008
10,097
85
#9
jfrodsham wrote:

> Hi, I poked around a bit on the new forum here, and didn't see too much
> about x64 support. On the old Sparklist forum Rex Conn jumped in and
> mentioned there was not much to be gained by an x64 version, but that it
> was being worked on. However, I have recently run in to some issues,
> that has brought me back here. When using 4NT 7.01.370, if I try and run
> some 64bit console apps I get errors with the software or even "file not
> found". The most recent problem was when I tried to run "sfc /scannow".
> I get this message: Windows Resource Protection could not start the
> repair service. If I run it from cmd.exe, it works fine. I have noticed
> when doing a directory listing some files won't show up with 4nt.exe,
> but I can see them in explorer or a cmd.exe prompt. Any ideas what might
> be wrong?
You need to set Wow64FSRedirection=NO in your 4NT.INI file.

Rex Conn
JP Software
 

samintz

Scott Mintz
May 20, 2008
1,203
11
Solon, OH, USA
#10
Is anyone else receiving this thread as raw HTML? I can barely read it
because of all the angle bracketed fields.

-Scott

"JP Software Forums" <neil@jpsoft.com> wrote on 09/22/2008 11:18:15 AM:


> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
> Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
> <html>
> <head>
> <style>
> <!--
body {
font-family: Verdana, Geneva, Arial, helvetica, sans-

}
table {
margin-top: 1em;
}
td {
font-family: Verdana,

> Geneva, Arial, helvetica, sans-serif;
font-size: 80%;
}
th {
font-

> family: Verdana, Geneva, Arial, helvetica, sans-serif;
font-size:

}
alt2 {
background-color: #FFFFFF;
font-family: Verdana,

> Geneva, Arial, helvetica, sans-serif;
font-size: 80%;
}
-->

> </style>
> </head>
> <body><div id="ei_body"><div style="margin:20px; margin-top:5px; ">
> <div class="smallfont" style="margin-bottom:2px">Quote:</div>
> <table cellpadding="6" cellspacing="0" border="0" width="100%">
> <tr>
> <td class="alt2" style="border:1px inset">
>
> <div>
> Originally Posted by <strong>Charles Dye</strong>
> <a href="showthread.php?p=2194#post2194"
> rel="nofollow"><img class="inlineimg" src="images/buttons/viewpost.
> gif" border="0" alt="View Post" /></a>
> </div>
> <div style="font-style:italic">Version 7 is getting
> pretty long in the tooth. You might try downloading version 9 and
> see if that one doesn't work better for you.</div>
>
> </td>
> </tr>
> </table>
> </div>I suppose I should have been more clear. I want to find out if
> my issues have been resolved before dropping the $50 bucks.<br />
> -j<br />
> </div>
> <div id="ei_sig"><br />
>
> </div>
> </body>
> </html>
 
#11
JP Software Forums" <neil@jpsoft.com>; "jfrodsham wrote:
| Update:
|
| It pays to RTFM..... I found the Win64 file system redirection
| override option. I still need the aspirin.

Glad you found the solution. Sorry, the problem is MS' refusal to provide
backward compatibility. You'd think they'd learn after 3 decades, but
arrogance wins.
--
Steve
 
Sep 21, 2008
9
0
#12
Unfortunately the Wow64FSRedirection option doesn't totally solve the problem. Executing this command from 4NT:

C:\Windows\System32>dir > out.txt

will still put out.txt in to the SysWOW64 folder no matter the setting. :( The main thing is I understand what is happening so I can work around it. I still think it would be nice to have x64 binaries for TCC etc...

-J
 

rconn

Administrator
Staff member
May 14, 2008
10,097
85
#13
jfrodsham wrote:

> Unfortunately the Wow64FSRedirection option doesn't totally solve the
> problem. Executing this command from 4NT:
>
> C:\Windows\System32>dir > out.txt
>
> will still put out.txt in to the SysWOW64 folder no matter the setting.
> The main thing is I understand what is happening so I can work around
> it. I still think it would be nice to have x64 binaries for TCC etc...
That is not 64-bit related -- Vista will not allow an app to write to
the \Windows directory and subdirectories (or "\program files") unless
the app is an installer.

Rex Conn
JP Software