Custom Query (44 matches)
Results (25 - 27 of 44)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#27 | fixed | ESET and BEGINLIBPATH/ENDLIBPATH | ||
Description |
Hi/2. ESET is a great feature of 4OS2. BTW, it does work with BEGINLIBPATH/ENDLIBPATH. Even if I modify them with ESET, its result is not applied actually. |
|||
#26 | invalid | Redirection issues | ||
Description |
From CMD.EXE, running the following command results in the expected output: DumpIDE b > report.dumpide 2-09-14 13:39 6,336 0 report.dumpide However, from 4OS2.EXE, we get a 0-length file: 2-09-14 14:17 0 0 report.dumpide I have tried all manner of stderr, stdout, etc. which come to mind, but no matter what I try, I cannot redirect the output of this particular executable to a file under 4OS2. For reference, the verison of DumpIDE.EXE I am using is: Signature: @#slainc:0.1#@##1## 2012/10/12 01:00:00 slamain::EN:US:0:U :@@dumpide utility (c) 2006 Daniela Engert, Copyright (c) 2012 Steven Levine and
Vendor: slainc Revision: 0.01 Date/Time?: 2012/10/12 01:00:00 Build Machine: slamain Language Code: EN Country Code: US Uniprocessor only File Version: 0.1 Description: dumpide utility (c) 2006 Daniela Engert, Copyright (c) 2012 Steven Levine and A FWIW, pipe doesn't seem to work, either: [c:\os2\apps\dani]type report.dumpide | grep 3249 18:00.00 1106:3249 IRQs: PCI:11 PIC: 0 APIC: 0 Found native mode VIA VT6421 SATA (1106/3249 rev 50) on 18:0.0 VendorID 1106, DeviceID 3249, Subsystem VendorID 1106, DeviceID 3249 [c:\os2\apps\dani]DumpIde.exe b | grep 3249 :-) |
|||
#25 | fixed | Add new internal variable: _TS (TimeStamp) | ||
Description |
Following onto my previous enhancement request (ticket #24), I propose a new internal variable, _TS, to return a formatted timestamp. Currently, Steve advises that he uses something like: %[_YEAR]%@right[2,0%_MONTH]%@right[2,0%_DAY]-%@right[2,0%_HOUR]%@right[2,0%_MINUTE] and sets that in an ENV var (SET TS=). By adding _TS as an internal variable and the associated TSFMT formatting template (per my suggestion in ticket #24): SET TSFMT=YYYY-MM-DD-HH-MM or SET TSFMT=YYYY-MM-DD-HH-MM-SS all that would be required would be to use a simple: %_TS to insert a timestamp of the desired precision on the command line or in a batch file. |