I cannot use links to .btm files

oph

Jun 28, 2008
39
0
Since a time I was nospool.btm to cancel printer jobs

@rem nospool.btm
net stop spooler del
%systemroot%\System32\Spool\impresoras\*.shd del
%systemroot%\System32\Spool\impresoras\*.spl del
%systemroot%\System32\Spool\PRINTERS\*.shd del
%systemroot%\System32\Spool\PRINTERS\*.spl net start spooler

I added a link in Desktop to access nospool, and it worked by two
years. I call this "link+mouse" mode.

But with the version 24, the link is not working, the Explorer and
Total Commander are ineffective, too. Only a short flash on screen and
nothing happen.

The command works, both TCMD and TCC process it and delete the spool
contents, "nospool <CR>"


If the link is to nospool.bat, with nospool.bat being identical to
nospool.btm, the link works.


There are other links to xx.btm that are not working, and a copy to
xx.bat fails too.

For example,

@rem apagar.btm
reboot /s

fails in "link+mouse" mode.

Is this a problem with the plane, or it is a pilot mistake (the more
probable)?.


OPH. 2018-12-22 09:06
 
May 20, 2008
9,444
63
Syracuse, NY, USA
Is this a problem with the plane, or it is a pilot mistake (the more
probable)?.
It might be the plane. With v24, build 29, on Win7/32, I have this (which is not correct).
Code:
v:\> assoc .btm
.btm=TCC.Batch

v:\> ftype tcc.batch
tcc.batch="" /c "%%1" %%*
It's better on Win10/64
Code:
tcc.batch="C:\apps\tc24\tcc.exe" /c "%%1" %%*
 
May 20, 2008
9,444
63
Syracuse, NY, USA
After fixing it once, I have this again (win7/32 only).
Code:
v:\> ftype tcc.batch
tcc.batch="" /c "%%1" %%*
Since this thread started on 12/22 and by b29 files (current) are dated 12/20 I can only presume the last time this happened was also with b29. What could be clobbering tcc.batch's shell\open action?
 
May 20, 2008
9,444
63
Syracuse, NY, USA
After fixing it once, I have this again (win7/32 only).
Code:
v:\> ftype tcc.batch
tcc.batch="" /c "%%1" %%*
Since this thread started on 12/22 and by b29 files (current) are dated 12/20 I can only presume the last time this happened was also with b29. What could be clobbering tcc.batch's shell\open action?
Never mind. I know what happened. I repaired the installation trying to fix the stuff mentioned in the "Yipes, pipes!" thread. So build 29 was installed again.