<?xml version="1.0" encoding="ISO-8859-1"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>DOS ain't dead</title>
<link>http://www.bttr-software.de/forum/</link>
<description>DOS ain't dead</description>
<language>en</language>
<item>
<title>&quot;SST - Seek Stopper&quot; -- Caching Needed, Too!</title>
<content:encoded><![CDATA[<i>Reply from Jack, 12.03.2010, 22:35:</i><br /><br /><i>&gt; On Wikipedia I found a link to the &quot;SST - Seek Stopper Hard Disk<br /></i><i>&gt; Optimizer&quot;, a very early defrag utility, which has been released<br /></i><i>&gt; to the public domain in 2005 (?) ...<br /></i>
<br />
I have used the 1998 &quot;Diskeeper&quot; for Windows/NT for over 10 years,<br />
which functions similarly to &quot;SST&quot;.<br />
<br />
Disk &quot;defragmenter&quot; programs can gain a bit faster hard-disk speed<br />
by re-arranging data, so no &quot;big&quot; seeks are necessary when reading<br />
existing files.   All sectors of a file are on the disk in &quot;linear<br />
order&quot;, thus extra seeks are avoided.<br />
<br />
Disk &quot;defragmenters&quot; do NOT help when writing files, as DOS cannot<br />
guarantee new files' sectors are written linearly.   DOS will give<br />
files the next &quot;free&quot; group of FAT-table sectors, which themselves<br />
may not be in linear order!   So multiple output files are usually<br />
written &quot;fragmented&quot;, i.e. part of file &quot;A&quot;, then part of file &quot;B&quot;<br />
etc.<br />
<br />
Also, &quot;defragmenters&quot; made sense in 1986, when hard-disks had seek<br />
times of about 5-msec on 1-track seeks and 30- to 50-msec averages<br />
for the entire hard-disk.   These times are 1-msec and 4.5-msec on<br />
&quot;modern&quot; hard-disk drives offered now!<br />
<br />
So, a &quot;defragmenter&quot; gets you only so far in improving disk speed.<br />
<br />
After a disk has been defragmented, one still needs a disk caching<br />
program with DOS.   DOS must still access the disk's directory and<br />
FAT tables for any file, and DOS is written for only single-sector<br />
directory I-O.   Reading/writing disks one sector at a time is NOT<br />
efficient, as it LOSES a disk revolution between each sector pair!<br />
Hard disks CAN do multi-sector I-O, but DOS still has its original<br />
1981 &quot;El Cheapo&quot; directory handling, which slows EVERYTHING down!!<br />
<br />
Such accesses are mostly eliminated if UIDE (or LBAcache/CDRcache,<br />
if appropriate) is used to CACHE directory and FAT data!    Actual<br />
file data will ALSO be cached, and thus a DOS system will run even<br />
faster.   FAT, directory, or file data that is &quot;in cache&quot; requires<br />
only a fast move from XMS memory (the cache), NOT a slow &quot;physical<br />
access&quot; of the hard-disk, diskette, or CD/DVD drive.<br />
<br />
DOS users should have BOTH a &quot;defragmenter&quot; AND a caching program!]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7755</link>
<pubDate>Fri, 12 Mar 2010 22:35:48 GMT</pubDate>
</item>
<item>
<title>&quot;SST - Seek Stopper Hard Disk Optimizer&quot; found</title>
<content:encoded><![CDATA[<i>Reply from RayeR, 12.03.2010, 02:13:</i><br /><br /><i>&gt; What DOS extender did AutoCAD use? Most good ones allow you to<br /></i><i>&gt; configure to use EMS or XMS, reducing conventional memory, if needed.)<br /></i>
<br />
It uses PharLap 386. There's CFIG386.EXE for some runtime settings of its EXE files.]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7754</link>
<pubDate>Fri, 12 Mar 2010 02:13:41 GMT</pubDate>
</item>
<item>
<title>NASM version 2.08.01 available</title>
<content:encoded><![CDATA[<i>Post by rr, 11.03.2010, 23:03:</i><br /><br />The NASM developers have released NASM version 2.08.01 on 10 March 2010.<br />
<br />
Home page: <a href="http://www.nasm.us/">http://www.nasm.us/</a><br />
Download: <a href="http://www.nasm.us/pub/nasm/releasebuilds/2.08.01/">http://www.nasm.us/pub/nasm/releasebuilds/2.08.01/</a><br />
<br />
Changes:<br />
• A number of enhancements/fixes in macros area.<br />
• Support for converting strings to tokens. See section 4.1.9.<br />
• Fuzzy operand size logic introduced.<br />
• Fix COFF stack overrun on too long export identifiers.<br />
• Fix Macho-O alignment bug.<br />
• Fix crashes with -fwin32 on file with many exports.<br />
• Fix stack overrun for too long [DEBUG id].<br />
• Fix incorrect sbyte usage in IMUL (hit only if optimization flag passed).<br />
• Append ending token for .stabs records in the ELF output format.<br />
• New NSIS script which uses ModernUI and MultiUser approach.<br />
• Visual Studio 2008 NASM integration (rules file).<br />
• Warn a user if a constant is too long (and as result will be stripped).<br />
• The obsoleted pre-XOP AMD SSE5 instruction set which was never actualized was removed.<br />
• Fix stack overrun on too long error file name passed from the command line.<br />
• Bind symbols to the .text section by default (ie in case if SECTION directive was omitted) in the ELF output format.<br />
• Fix sync points array index wrapping.<br />
• A few fixes for FMA4 and XOP instruction templates.<br />
• Add AMD Lightweight Profiling (LWP) instructions.<br />
• Fix the offset for %arg in 64-bit mode.<br />
• An undefined local macro (%$) no longer matches a global macro with the same name.<br />
• Fix NULL dereference on too long local labels.]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7753</link>
<pubDate>Thu, 11 Mar 2010 23:03:04 GMT</pubDate>
</item>
<item>
<title>GZIPDATE.REX (uses TOUCH)</title>
<content:encoded><![CDATA[<i>Reply from Rugxulo, 11.03.2010, 19:41:</i><br /><br /><i>&gt; FYI, PC Magazine also created 2 touch utils which were available as<br /></i><i>&gt; follows:<br /></i><i>&gt; touch.com   (v7n07.zip) - assembler version with soruce by Michael J.<br /></i><i>&gt; Mefford<br /></i><i>&gt; touchw.exe  (v8n02.zip) - C version by ?? (C ver doesn't like readonly<br /></i><i>&gt; files!)<br /></i><i>&gt; <br /></i><i>&gt; But sadly I am not going to link to either. The reason why if<br /></i><i>&gt; my memory serves me correctly is comes down the publisher of PC Mag (Ziff<br /></i><i>&gt; Davis) deciding in the mid 90's to contact simtel (and mirrors) and<br /></i><i>&gt; legally ask them to remove all the PC Mag utils which at the time were<br /></i><i>&gt; widely available.<br /></i>
<br />
Yes, I'm aware of that, and yes it's a little silly, considering it limits the usefulness, but oh well, we can't have everything, can we?  :-/<br />
<br /><i>&gt; &gt; if not creating a new file (which -C forbids), why open for read/write<br /></i><i>&gt; &gt; (3D02)??<br /></i><i>&gt; <br /></i><i>&gt; No doubt for safety, since read-only is effectively saying &quot;don't touch me&quot;.<br /></i>
<br />
Except I never thought of readonly in that way. +R usually means (to me) &quot;don't modify the file data&quot; whereas touch only changes the file's time (in the file system itself). It's very rare that someone would accidentally touch a readonly file, but to fair that's why it should probably be optional (e.g. DR-DOS /R or 4DOS /F or FD-TOUCH /C here).<br />
<br /><i>&gt; &gt; debug touch2.com &lt; %0<br /></i><i>&gt; <br /></i><i>&gt; I seem to remember this may fail on some (newer?) DOS shells and you need<br /></i><i>&gt; to do %0.bat on those otherwise the file is NOT found.<br /></i>
&gt;<br /><i>&gt; <code>if exist .\%0 call debug &lt;%0<br /></i><i>&gt; if exist .\%0.bat call debug &lt;%0.bat</code><br /></i>
<br />
Yes, that's why I did this at the top (see below).  :-)<br />
<br />
<code>if not exist %0 %0.bat</code><br />
<br />
BTW, GNU touch (Coreutils, formerly Fileutils, e.g. DJGPP's FIL41B.ZIP) seems to not have the +r bug. However, in my limited experience, it's weird in what it accepts. FreeDOS touch is more forgiving. Heck, even DR-DOS touch whines if you don't specify the year correctly despite the help usage (needs four-digit year or maybe two, I forget). Charles Dye's version is good, but it has no LFN support nor +r override (though it lets you change attributes ... but I dislike removing +r for no good reason).<br />
<br />
FreeDOS touch is written in TASM (boo hiss ... but I did a temporary quick hack to NASM which I will have to polish up if anyone cares), but at least it supports various non-US date formats, assemble-time NLS, switchars (anybody use that?), no file lists, no LFNs, DOS 2.0 compatible (QUALPATH.ASM seems to mimic int 21h,60h [DOS 3+]), but only changes modification time (not FAT32 access or creation time). In other words, the best touch util is probably the one in 4DOS, but not everybody uses 4DOS, and it's quite a big util to use just for touching files.  ;-)<br />
<br />
P.S. Slightly annoying that you have to use a file handle to touch a file instead of a pointer to ASCIIZ, but I guess &quot;open + touch&quot; isn't so much to ask.<br />
<br />
EDIT:  See <a href="http://www.delorie.com/djgpp/doc/rbinter/ix/21/57.html">int 21h, 57xxh</a> or <a href="http://www.delorie.com/djgpp/doc/rbinter/id/14/32.html">7143h</a><br />
<br />
EDIT #2: For the record, I'm pretty sure FreeDOS doesn't update FAT32 time/date-stamps besides creation.]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7752</link>
<pubDate>Thu, 11 Mar 2010 19:41:53 GMT</pubDate>
</item>
<item>
<title>&quot;SST - Seek Stopper Hard Disk Optimizer&quot; found</title>
<content:encoded><![CDATA[<i>Reply from Rugxulo, 11.03.2010, 19:25:</i><br /><br /><i>&gt; &gt; On Wikipedia I found a link to the &quot;SST - Seek Stopper Hard Disk<br /></i><i>&gt; &gt; Optimizer&quot;, a very early defrag utility,<br /></i><i>&gt; <br /></i><i>&gt; Very interesting find.<br /></i>
<br />
Yet another (Turbo) Pascal gem: &quot;defrag 10 MB HD in 8 minutes&quot;, no small feat considering the slow cpus of the day! Even though it's limited to 32 MB (FAT12), it's still interesting.<br />
<br />
To be honest, (on a semi-related note) I wonder why more tools don't use the FAT directly for greater speed. I guess nobody wants to write their own FAT12/16/32-specific routines (reinvent the wheel), esp. when direct sector access won't work under Windows anyways. Charles Dye's <a href="http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/file/">LOCATE</a> does, though, providing greater speed. (I also wonder if some DOS extenders would benefit from this, e.g. wouldn't be limited to 64k at a time when reading from files.)<br />
<br /><i>&gt; &gt; I didn't try running or building this tool. Maybe it's useful to<br /></i><i>&gt; someone.<br /></i>
<br />
Well, we do have <a href="http://www.freedos.org/software/?prog=defrag">FreeDOS Defrag</a>, which supports other FATs (-16, -32), albeit slowly, but this is a good alternative for reference.  ;-)<br />
<br /><i>&gt; The same author of SST; Alfred J. Heyman has also kindly made the source<br /></i><i>&gt; available for at least one other program:<br /></i><i>&gt; <a href="http://www.spectrum-research.com/V2/projects_bigshell.asp">BigShell<br /></i><i>&gt; for autocad</a><br /></i>
<br />
Now this is confusing. I guess the larger code size (32-bit) meant less conventional memory free, thus his need to work around it. I didn't really look too closely, but I'm blindly guessing his shell (when run first) saves the state then &quot;restores&quot; it by dumping out / overwriting AutoCAD in memory. (What DOS extender did AutoCAD use? Most good ones allow you to configure to use EMS or XMS, reducing conventional memory, if needed.)]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7751</link>
<pubDate>Thu, 11 Mar 2010 19:25:00 GMT</pubDate>
</item>
<item>
<title>GZIPDATE.REX (uses TOUCH)</title>
<content:encoded><![CDATA[<i>Reply from Arjay, 11.03.2010, 17:09:</i><br /><br /><i>&gt; However, the main issue I have with it (among other touch utils) is that<br /></i><i>&gt; none seem to allow touching a read-only file! Why? I can't imagine that's<br /></i><i>&gt; really a worthwhile protection. At least two (DR-DOS' TOUCH.EXE and 4DOS's<br /></i><i>&gt; built-in TOUCH) support overriding it (/R or /F, respectively) but most<br /></i><i>&gt; others don't (even Charles Dye's improved version).<br /></i>
<br />
FYI, PC Magazine also created 2 touch utils which were available as follows:<br />
touch.com   (v7n07.zip) - assembler version with soruce by Michael J. Mefford<br />
touchw.exe  (v8n02.zip) - C version by ?? (C ver doesn't like readonly files!)<br />
<br />
I only ever used Michael J. Mefford version which from memory never had any problems with read-only files.  As for the later C version I have only just come across it whilst relocating these files now and according to the C source it doesn't handle readonly files.... it looks rubbish in comparism to Micheal's earlier assembler version - all of his work was always great IMHO!<br />
<br />
But sadly I am not going to link to either.  Why?  Well in the past PC Mag utils were distributed not only with their magazines and but also widely across Bulletin Boards and ftp sites like <a href="http://en.wikipedia.org/wiki/Simtel">simtel.net</a>. Sadly getting hold of PC Mags early utils now days is no longer easy.  The reason why if my memory serves me correctly is comes down the publisher of PC Mag (Ziff Davis) deciding in the mid 90's to contact simtel (and mirrors) and legally ask them to remove all the PC Mag utils which at the time were widely available.  Thus you will find their utils coming back in most cases but without the underlying files which were removed.<br />
<br />
I was never a contacted directly myself but remember this all vaguely as I ran a BBS distributing <a href="http://en.wikipedia.org/wiki/Demoscene">demos</a><br />
and also mirroring a lot of Simtel content using <a href="http://en.wikipedia.org/wiki/Walnut_Creek_CDROM">Walnut creek's CD-ROM</a>'s designed for that purpose!  <br />
<br />
I seem to remember PC Mag's utils may have then been available online on their website to &quot;existing&quot; PC Magazine customers via their archive but as I'm not an existing customer I don't know if this is indeed still the case.  <br />
<br />
I was fortunately also a regular PC Mag customer in the past who purchased several years worth of their magazines with their coverdisks.  In otherwords I have own legal original copies of their utils in addition to CD-ROM's etc.  <br />
<br />
<br /><i>&gt; There's also no common way to easily preserve file attributes before<br /></i><i>&gt; touching in order to be restored afterwards either, <br /></i>
<br />
Hmmm, noted.  Remind me of this again in the future for RJDOS (or whatever it might be renamed to) as I'm planning/working on some similiar save/restore features which I could re-implement for attributes etc.  In short what I'm working to include (long term) is things like save interrupts, run process, restore interrupts - why?  Well for several reasons: 1) provide features to *flag* this type of behaviour.  2) To help provide work arounds for bugs.<br />
Importantly I'm planning to do this across DOS versions as much as possible.<br />
<br />
Still back to touch....<br />
<br />
<br /><i>&gt; if not creating a new file (which -C forbids), why open for read/write<br /></i><i>&gt; (3D02)??<br /></i>
<br />
No doubt for safety, since read-only is effectively saying &quot;don't touch me&quot;.<br />
<br />
<br /><i>&gt; Feedback welcome.   :-)<br /></i><i>&gt; debug touch2.com &lt; %0<br /></i>
<br />
I seem to remember this may fail on some (newer?) DOS shells and you need to do %0.bat on those otherwise the file is NOT found.  I can't remember off the top of my head what/where but I definately remember running into that problem.<br />
<br />
Last time I ran into this I seem to remember writting lines to test and try both, e.g.  something like this (note basic &quot;concept&quot; code below not actual):<br />
<br />
<code>if exist .\%0 call debug &lt;%0<br />
if exist .\%0.bat call debug &lt;%0.bat</code><br />
<br />
that way trapping both instances and still allowing ppl to rename the BATch.<br />
As above I can't remember which DOS shell or how/why off the top of my head and the above code is just a non-working example to provide an example.]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7750</link>
<pubDate>Thu, 11 Mar 2010 17:09:10 GMT</pubDate>
</item>
<item>
<title>&quot;SST - Seek Stopper Hard Disk Optimizer&quot; found</title>
<content:encoded><![CDATA[<i>Reply from Arjay, 11.03.2010, 16:13:</i><br /><br /><i>&gt; On Wikipedia I found a link to the &quot;SST - Seek Stopper Hard Disk<br /></i><i>&gt; Optimizer&quot;, a very early defrag utility,<br /></i>
<br />
Very interesting find.  See also Alfred's informative page about <a href="http://www.spectrum-research.com/V2/projects_dsoptimize.asp">DS Optimize</a> which is what <a href="http://www.spectrum-research.com/V2/projects_sst.asp">SST</a> became - sadly currently without the source!<br />
<br /><i>&gt; It was written in Turbo Pascal 3.0, <br /></i>
<br />
which (for anyone who doesn't know) is now freely available from &quot;Borland's museum&quot; which is now here: <a href="http://edn.embarcadero.com/museum">http://edn.embarcadero.com/museum</a> - a nice easy to remember URL.... or search &quot;Borland Museum&quot; ;-)<br />
<br /><i>&gt; I didn't try running or building this tool. Maybe it's useful to someone.<br /></i>
<br />
The same author of SST; Alfred J. Heyman has also kindly made the source available for at least one other program: <a href="http://www.spectrum-research.com/V2/projects_bigshell.asp">BigShell for autocad</a> (<a href="http://www.spectrum-research.com/publish/bigshell/default.htm">ASM/C source</a>)  See also other project tabs for interesting background on his other legacy programs (without source) and newer systems.  Thanks Alfred!]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7749</link>
<pubDate>Thu, 11 Mar 2010 16:13:49 GMT</pubDate>
</item>
<item>
<title>AHCI projects?</title>
<content:encoded><![CDATA[<i>Reply from DOSferatu, 10.03.2010, 16:57:</i><br /><br /><i>&gt; This weekend I tried the AHCI.SYS driver from Hewlett packard with my new<br /></i><i>&gt; notebook HP Pavilon dv6 and it didn't worked :confused: <br /></i><i>&gt; In BIOS I can't set almost nothing so it is very bad.<br /></i><i>&gt; Now I want to try to modify the BIOS with Phoenix Bios Editor<br /></i>
<br />
Do you know if you have an AHCI compatible controller in your notebook?  There may be a very good reason that it didn't work. ;)  <br />
<br />
Do a PCI device scan, AHCI controllers have PCI registers 9,a,b = 01,06,01]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7748</link>
<pubDate>Wed, 10 Mar 2010 16:57:20 GMT</pubDate>
</item>
<item>
<title>&quot;SST - Seek Stopper Hard Disk Optimizer&quot; found</title>
<content:encoded><![CDATA[<i>Post by rr, 08.03.2010, 22:36:</i><br /><br />On Wikipedia I found a link to the &quot;SST - Seek Stopper Hard Disk Optimizer&quot;, a very early defrag utility, which has been released to the public domain in 2005 (?).<br />
It was written in Turbo Pascal 3.0, but, due to its age, only supports partitions &lt;32 MiB. So be careful!<br />
<br />
I didn't try running or building this tool. Maybe it's useful to someone.<br />
<br />
Homepage w/ sources: <a href="http://www.spectrum-research.com/V2/projects_sst.asp">http://www.spectrum-research.com/V2/projects_sst.asp</a><br />
Shareware binary: <a href="ftp://garbo.uwasa.fi/pc/diskutil/sst201.zip">sst201.zip</a>]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7747</link>
<pubDate>Mon, 08 Mar 2010 22:36:06 GMT</pubDate>
</item>
<item>
<title>AHCI projects?</title>
<content:encoded><![CDATA[<i>Reply from Laaca, 08.03.2010, 09:41:</i><br /><br />This weekend I tried the AHCI.SYS driver from Hewlett packard with my new notebook HP Pavilon dv6 and it didn't worked :confused: <br />
In BIOS I can't set almost nothing so it is very bad.<br />
Now I want to try to modify the BIOS with Phoenix Bios Editor]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7746</link>
<pubDate>Mon, 08 Mar 2010 09:41:09 GMT</pubDate>
</item>
<item>
<title>HX 2.17 quirk -- R4 (REXX) only accepts uppercase words</title>
<content:encoded><![CDATA[<i>Reply from Rugxulo, 02.03.2010, 04:07:</i><br /><br /><i>&gt; presumably also with FreeDOS)<br /></i>
<br />
Apparently not! It seems to work there fine. So I dunno why. Weird.  :-|]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7745</link>
<pubDate>Tue, 02 Mar 2010 04:07:58 GMT</pubDate>
</item>
<item>
<title>GZIPDATE.REX (uses TOUCH)</title>
<content:encoded><![CDATA[<i>Reply from Rugxulo, 02.03.2010, 01:22:</i><br /><br />And here's why I'm using TOUCH at all:<br />
<br />
<code>/* REXX */<br />
<br />
if arg() = 0 then do<br />
say ''<br />
say 'GZIPDATE.REX -- view or touch .gz file''s stored internal *nix date'<br />
say '( requires Regina or BRexx )'<br />
say ''<br />
say 'gzipdate [-t] myfile.tgz'<br />
say ''<br />
say '-t&nbsp; &nbsp;touch (else only views internal date; uses external TOUCH.COM)'<br />
say ''<br />
exit 255<br />
end<br />
<br />
parse arg option filename<br />
parse version ver<br />
<br />
if pos('Regina',ver) = 0 &amp; pos('brexx',ver) = 0 then do<br />
say ''<br />
say 'Regina or BRexx required!'<br />
exit 1<br />
end<br />
<br />
if option \= '-t' then filename = option<br />
<br />
if filename = '' then do<br />
say ''<br />
say 'No .GZ file specified!'<br />
exit 2<br />
end<br />
<br />
ch = charin(filename,1,2)<br />
if ch \= '1f'x || '8b'x then do<br />
say ''<br />
say 'Not a valid .GZ file!'<br />
exit 3<br />
end<br />
<br />
ch = charin(filename,5,4)<br />
mydate = c2d(reverse(ch))<br />
<br />
if pos('Regina',ver) \= 0 then ,<br />
newdate = date('U',mydate,'T')&nbsp; &nbsp; &nbsp;/* Unix-&gt;USA, not ANSI !! */<br />
<br />
if pos('brexx',ver) \= 0 then do<br />
if import('dates.r') = 0 then do<br />
newdate = GMTime(mydate)<br />
newdate = delstr(newdate,pos(' ',newdate))<br />
parse var newdate year 5 6 monthday<br />
newdate = monthday'/'year<br />
end<br />
else do<br />
say ''<br />
say 'Can''t find BRexx''s dates.r'<br />
exit 4<br />
end<br />
end<br />
<br />
say newdate&nbsp; &nbsp;/* Regina: 02/21/10&nbsp; BRexx: 2/21/2010 */<br />
<br />
/*<br />
using Kris Heidenstrom's TOUCH.COM for FreeDOS<br />
<a href="http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/...">http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/...</a><br />
&nbsp; &nbsp; &nbsp; /1.0/pkgs/touch[xs].zip<br />
*/<br />
<br />
if option = '-t' then do<br />
'dir' filename<br />
'touch' newdate filename<br />
'dir' filename<br />
end<br />
<br />
/* EOF */</code>]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7744</link>
<pubDate>Tue, 02 Mar 2010 01:22:13 GMT</pubDate>
</item>
<item>
<title>TOUCH.COM 1.4.3 (minor fix: debug script)</title>
<content:encoded><![CDATA[<i>Post by Rugxulo, 02.03.2010, 01:10:</i><br /><br />FreeDOS' TOUCH.COM works fine and is well-written (IMHO) although it still needs some tweaking (e.g. convert to NASM or FASM, add LFN support).<br />
<br />
However, the main issue I have with it (among other touch utils) is that none seem to allow touching a read-only file! Why? I can't imagine that's really a worthwhile protection. At least two (DR-DOS' TOUCH.EXE and 4DOS's built-in TOUCH) support overriding it (/R or /F, respectively) but most others don't (even Charles Dye's improved version). <br />
<br />
There's also no common way to easily preserve file attributes before touching in order to be restored afterwards either, so that's bad for .BAT files. Anyways, in the interest of simplicity (and because it's a minor fix), I wrote a debug script instead of updating the TASM srcs. In short, if not creating a new file (which -C forbids), why open for read/write (3D02)??<br />
<br />
Feedback welcome.   :-)<br />
<br />
<code>@echo off<br />
if not exist %0 %0.bat<br />
if not exist touch.com goto end<br />
if not exist touch2.com copy /b touch.com touch2.com<br />
attrib -r touch2.com<br />
debug touch2.com &lt; %0<br />
goto end<br />
<br />
; patch for Kris Heidenstrom's TOUCH.COM 1.4.3 (for FreeDOS)<br />
; Monday 01 March 2010, rugxulo _AT_ gmail _DOT_ com<br />
<br />
; what it does: lets -C also permit touching readonly +R files<br />
; int 21h,3D '02'h (read/write) fails to open on +R files<br />
<br />
; TODO: convert whole program from TASM to FASM; fix this; add LFN support<br />
<br />
;NewCall=09C0<br />
;NewEOF=0145h<br />
;Patch=0146h<br />
;CFlag=058Eh<br />
;ret=0151h<br />
<br />
; (only if you want to bump the version number to 1.4.'4' for -F)<br />
;e 127<br />
;34<br />
<br />
a 09C0<br />
; former home of &quot;mov ax,3D02&quot;, patched with call to fix<br />
call 0146<br />
<br />
a 0145<br />
; = 13 bytes below<br />
; (1Ah = EOF / Ctrl-Z marker for &quot;type&quot;)<br />
db 1A<br />
mov ax,3D02<br />
test byte ptr [058E],1<br />
jz 0151<br />
; salc<br />
db D6<br />
ret<br />
<br />
w<br />
Q<br />
Q<br />
<br />
:end<br />
for %%a in (touch touch2) do if not exist %%a.com goto bye<br />
dir touch*.com | find /i &quot;com&quot;<br />
echo on<br />
REM ... generate an error (to prove it didn't work before)<br />
attrib +r touch.com<br />
touch2 touch.com<br />
REM ... try again with -C (to prove it works now)<br />
touch2 -C touch.com<br />
@echo off<br />
dir touch*.com | find /i &quot;com&quot;<br />
:bye</code><br />
<br />
EDIT: Changed &quot;.com&quot; to &quot;com&quot; for some DOS shells.]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7743</link>
<pubDate>Tue, 02 Mar 2010 01:10:44 GMT</pubDate>
</item>
<item>
<title>HX 2.17 quirk -- R4 (REXX) only accepts uppercase words</title>
<content:encoded><![CDATA[<i>Post by Rugxulo, 02.03.2010, 00:43:</i><br /><br />R4 (REXX) on Win32 behaves normally. But in DR-DOS + HX 2.17 (and presumably also with FreeDOS), it seems to only work with uppercase. (DOSBox isn't a problem either, so it's not a valid comparison there, sadly.)<br />
<br />
echo parse version ver ; say ver &gt; test.rex<br />
echo PARSE VERSION VER ; SAY VER &gt; test2.rex<br />
r4 test.rex<br />
<br />
REXX-r4 4.00 28 Jan 2007<br />
<br />
<a href="http://www.kilowattsoftware.com/r4Page.htm">http://www.kilowattsoftware.com/r4Page.htm</a>]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7742</link>
<pubDate>Tue, 02 Mar 2010 00:43:55 GMT</pubDate>
</item>
<item>
<title>WDE in NTVDM</title>
<content:encoded><![CDATA[<i>Reply from Japheth, 22.02.2010, 09:32:</i><br /><br /><i>&gt; ... it runs in NTVDM now ( exception: CDROM raw mode ). ...<br /></i>
<br />
CD-ROM raw mode is supported now. Also, there was an error message if the drive to access was an USB memory stick - apparently NTVDM doesn't like DOS lock commands for such drives. This has also been fixed.]]></content:encoded>
<link>http://www.bttr-software.de/forum/forum_entry.php?id=7741</link>
<pubDate>Mon, 22 Feb 2010 09:32:48 GMT</pubDate>
</item>
</channel>
</rss>