Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.msdos.programmer

comp.os.msdos.programmer

4482 articles, 681 threads (numbers 62 – 4553) — flat view

| Advanced

Subject Author Date
Emacs 19.34 DOS 6.22 won't come up vjp2.at@at.BioStrategist.dot.dot.com 2023-06-28 17:40 +0000
 
OAKCDROM no drive MSCDEX no driver (4 replies — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-06-26 18:40 +0000
   → Re: OAKCDROM no drive MSCDEX no driver "Auric__" <not.my.real@email.address> 2023-06-26 23:05 +0000
     → Re: OAKCDROM no drive MSCDEX no driver vjp2.at@at.BioStrategist.dot.dot.com 2023-06-26 23:49 +0000
       → Re: OAKCDROM no drive MSCDEX no driver "Auric__" <not.my.real@email.address> 2023-06-27 17:42 +0000
   → Re: OAKCDROM no drive MSCDEX no driver JJ <jj4public@outlook.com> 2023-06-27 17:51 +0700
 
link order (1 reply — unroll) "muta...@gmail.com" <mutazilah@gmail.com> 2023-06-23 00:59 -0700
   → Re: link order "muta...@gmail.com" <mutazilah@gmail.com> 2023-06-23 02:59 -0700
 
DOS 6.22 versions of ANSI.sys and MSCDEX (1 reply — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-06-22 19:18 +0000
   → Re: DOS 6.22 versions of ANSI.sys and MSCDEX Sjouke Burry <burrynulnulfour@ppllaanneett.nnll> 2023-06-22 22:06 +0200
 
mscdex (1 reply — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-06-20 19:56 +0000
   → Re: mscdex Steve Nickolas <usotsuki@buric.co> 2023-06-20 17:18 -0400
 
Where does cwsdpmi go for emacs (3 replies — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-06-18 19:46 +0000
   → Re: Where does cwsdpmi go for emacs rugxulo <rugxulo@gmail.com> 2023-06-19 00:57 -0700
     → Re: Where does cwsdpmi go for emacs vjp2.at@at.BioStrategist.dot.dot.com 2023-06-20 13:37 +0000
       → Re: Where does cwsdpmi go for emacs vjp2.at@at.BioStrategist.dot.dot.com 2023-06-20 19:53 +0000
 
family API (3 replies — unroll) "muta...@gmail.com" <mutazilah@gmail.com> 2023-06-18 02:31 -0700
   → Re: family API JJ <jj4public@outlook.com> 2023-06-19 00:51 +0700
     → Re: family API "muta...@gmail.com" <mutazilah@gmail.com> 2023-06-19 17:14 -0700
       → Re: family API "muta...@gmail.com" <mutazilah@gmail.com> 2023-06-20 02:00 -0700
 
clisp for msdos vjp2.at@at.BioStrategist.dot.dot.com 2023-06-18 19:47 +0000
 
boot.ini (4 replies — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-06-06 13:00 +0000
   → Re: boot.ini "Kerr-Mudd, John" <admin@127.0.0.1> 2023-06-06 22:07 +0100
     → Re: boot.ini vjp2.at@at.BioStrategist.dot.dot.com 2023-06-15 19:10 +0000
       → Re: boot.ini vjp2.at@at.BioStrategist.dot.dot.com 2023-06-18 19:45 +0000
   → Re: boot.ini JJ <jj4public@outlook.com> 2023-06-07 04:13 +0700
 
DOC or PDF to TXT (2 replies — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-06-16 18:53 +0000
   → Re: DOC or PDF to TXT ctosian <csynt8bit@gmail.com> 2023-06-17 04:07 -0700
     → Re: DOC or PDF to TXT vjp2.at@at.BioStrategist.dot.dot.com 2023-06-18 19:44 +0000
 
DOS extension proposal (6 replies — unroll) "muta...@gmail.com" <mutazilah@gmail.com> 2023-05-20 21:07 -0700
   → Re: DOS extension proposal "muta...@gmail.com" <mutazilah@gmail.com> 2023-05-20 22:46 -0700
     → Re: DOS extension proposal "muta...@gmail.com" <mutazilah@gmail.com> 2023-05-20 23:36 -0700
       → Re: DOS extension proposal "muta...@gmail.com" <mutazilah@gmail.com> 2023-05-20 23:45 -0700
         → Re: DOS extension proposal "muta...@gmail.com" <mutazilah@gmail.com> 2023-05-20 23:56 -0700
   → Re: DOS extension proposal JJ <jj4public@outlook.com> 2023-05-21 17:35 +0700
     → Re: DOS extension proposal "muta...@gmail.com" <mutazilah@gmail.com> 2023-05-21 14:23 -0700
 
Re: Small Tetris (2 replies — unroll) "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2021-12-04 20:44 +0000
   → Re: Small Tetris "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2021-12-14 10:25 +0000
     → Re: Small Tetris "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-05-19 18:18 +0100
 
Re: Creating links in DOS. (Oh dear, this is a long one...) (3 replies — unroll) KP2 KP2 <jungletrain@outlook.com> 2023-04-23 14:09 -0700
   → Re: Creating links in DOS. (Oh dear, this is a long one...) "Auric__" <not.my.real@email.address> 2023-04-24 16:14 +0000
     → Re: Creating links in DOS. (Oh dear, this is a long one...) arnold@hooterville.invalid (Arnold Ziffel) 2023-05-08 07:38 +0000
       → Re: Creating links in DOS. (Oh dear, this is a long one...) "Kerr-Mudd, John" <admin@127.0.0.1> 2023-05-08 10:21 +0100
 
Kenny Code for DOS "Kerr-Mudd, John" <admin@127.0.0.1> 2023-04-24 10:04 +0100
 
Re: CM3 revisited (13 replies — unroll) "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-02-26 12:17 +0000
   → Re: CM3 revisited Terje Mathisen <terje.mathisen@nospicedham.tmsw.no> 2023-02-26 20:33 +0100
     → Re: CM3 revisited "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-02-26 21:03 +0000
       → Re: CM3 revisited Terje Mathisen <terje.mathisen@nospicedham.tmsw.no> 2023-02-27 10:47 +0100
       → Re: CM3 revisited "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-03-03 19:56 +0000
         → Re: CM3 revisited Johann 'Myrkraverk' Oskarsson <johann@nospicedham.myrkraverk.invalid> 2023-03-04 05:36 +0800
           → Re: CM3 revisited "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-03-04 10:44 +0000
             → Re: CM3 revisited "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-03-04 17:06 +0000
               → Re: CM3 revisited Terje Mathisen <terje.mathisen@nospicedham.tmsw.no> 2023-03-05 14:45 +0100
                 → Re: CM3 revisited "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-03-05 16:29 +0000
                 → Re: CM3 revisited Terje Mathisen <terje.mathisen@nospicedham.tmsw.no> 2023-03-06 11:35 +0100
                 → Re: CM3 revisited "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-03-11 20:44 +0000
         → Re: CM3 revisited Terje Mathisen <terje.mathisen@nospicedham.tmsw.no> 2023-03-03 22:38 +0100
           → Re: CM3 revisited "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2023-03-04 10:46 +0000
 
Another attempt to rewrite DOS, piece-by-piece... (10 replies — unroll) Steve Nickolas <usotsuki@buric.co> 2022-07-09 16:29 -0400
   → Re: Another attempt to rewrite DOS, piece-by-piece... "Kerr-Mudd, John" <admin@127.0.0.1> 2022-07-09 22:14 +0100
     → Re: Another attempt to rewrite DOS, piece-by-piece... Steve Nickolas <usotsuki@buric.co> 2022-07-09 17:39 -0400
   → Re: Another attempt to rewrite DOS, piece-by-piece... Ben Collver <bencollver@tilde.pink> 2022-07-10 01:34 +0000
     → Re: Another attempt to rewrite DOS, piece-by-piece... Steve Nickolas <usotsuki@buric.co> 2022-07-09 22:25 -0400
   → Re: Another attempt to rewrite DOS, piece-by-piece... John McCue <jmccue@neutron.hsd1.ma.comcast.net> 2022-07-10 02:37 +0000
   → Re: Another attempt to rewrite DOS, piece-by-piece... Mateusz Viste <mateusz@xyz.invalid> 2022-07-10 16:24 +0200
   → Re: Another attempt to rewrite DOS, piece-by-piece... Steve Nickolas <usotsuki@buric.co> 2022-07-29 23:58 -0400
     → Re: Another attempt to rewrite DOS, piece-by-piece... Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> 2023-03-03 16:54 +0800
       → Re: Another attempt to rewrite DOS, piece-by-piece... Steve Nickolas <usotsuki@buric.co> 2023-03-03 08:54 -0500
         → Re: Another attempt to rewrite DOS, piece-by-piece... Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> 2023-03-04 00:07 +0800
 
Creating Assemblers Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> 2023-03-01 22:42 +0800
 
MSCDEX and cdrom...sys for vostro 3560 (2 replies — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-02-26 20:13 +0000
   → Re: MSCDEX and cdrom...sys for vostro 3560 Grant Taylor <gtaylor@tnetconsulting.net> 2023-02-26 17:23 -0700
   → Re: MSCDEX and cdrom...sys for vostro 3560 JJ <jj4public@outlook.com> 2023-02-28 01:12 +0700
 
Multiboot with MSDOS (1 reply — unroll) vjp2.at@at.BioStrategist.dot.dot.com 2023-01-19 20:20 +0000
   → Re: Multiboot with MSDOS vjp2.at@at.BioStrategist.dot.dot.com 2023-01-20 15:09 +0000
 
Re: Convert .PRN file to .TXT (4 replies — unroll) Abdul Aziz <abduldblogger@gmail.com> 2022-12-29 01:27 -0800
   → Re: Convert .PRN file to .TXT JJ <jj4public@outlook.com> 2022-12-29 21:58 +0700
   → Re: Convert .PRN file to .TXT Tavis Ormandy <taviso@gmail.com> 2022-12-29 15:13 +0000
   → Re: Convert .PRN file to .TXT "R.Wieser" <address@not.available> 2022-12-29 17:03 +0100
   → Re: Convert .PRN file to .TXT Johann Klammer <klammerj@NOSPAM.a1.net> 2023-01-01 18:26 +0100
 
Re: Dave Williams/DOSREF (2 replies — unroll) devlin.sakey@gmail.com 2014-04-12 03:49 -0700
   → Re: Dave Williams/DOSREF Daniel Hamilton <bitslasher@gmail.com> 2022-12-10 19:13 -0800
     → Re: Dave Williams/DOSREF ctosian <csynt8bit@gmail.com> 2022-12-13 04:46 -0800
 
retf (1 reply — unroll) "muta...@gmail.com" <mutazilah@gmail.com> 2022-11-06 14:16 -0800
   → Re: retf "muta...@gmail.com" <mutazilah@gmail.com> 2022-11-06 15:23 -0800
 
text mode for open (2 replies — unroll) "muta...@gmail.com" <mutazilah@gmail.com> 2022-10-21 21:04 -0700
   → Re: text mode for open Steve Nickolas <usotsuki@buric.co> 2022-10-22 01:44 -0400
     → Re: text mode for open "muta...@gmail.com" <mutazilah@gmail.com> 2022-10-21 23:07 -0700
 
Looking for .COM program sources in NASM Assembly (11 replies — unroll) Paolo Amoroso <paolo.amoroso@gmail.com> 2022-09-04 03:48 -0700
   → Re: Looking for .COM program sources in NASM Assembly "Kerr-Mudd, John" <admin@127.0.0.1> 2022-09-04 14:05 +0100
   → Re: Looking for .COM program sources in NASM Assembly Steve Nickolas <usotsuki@buric.co> 2022-09-04 12:47 -0400
     → Re: Looking for .COM program sources in NASM Assembly Paolo Amoroso <paolo.amoroso@gmail.com> 2022-09-05 00:39 -0700
     → Re: Looking for .COM program sources in NASM Assembly "Kerr-Mudd, John" <admin@127.0.0.1> 2022-09-05 10:54 +0100
       → Re: Looking for .COM program sources in NASM Assembly Steve Nickolas <usotsuki@buric.co> 2022-09-05 15:46 -0400
   → Re: Looking for .COM program sources in NASM Assembly Herbert Kleebauer <klee@unibwm.de> 2022-09-06 00:03 +0200
     → Re: Looking for .COM program sources in NASM Assembly Herbert Kleebauer <klee@unibwm.de> 2022-09-06 00:05 +0200
       → Re: Looking for .COM program sources in NASM Assembly "Kerr-Mudd, John" <admin@127.0.0.1> 2022-09-06 10:09 +0100
         → Re: Looking for .COM program sources in NASM Assembly Herbert Kleebauer <klee@unibwm.de> 2022-09-07 10:11 +0200
     → Re: Looking for .COM program sources in NASM Assembly Paolo Amoroso <paolo.amoroso@gmail.com> 2022-09-06 00:00 -0700
       → Re: Looking for .COM program sources in NASM Assembly Herbert Kleebauer <klee@unibwm.de> 2022-09-07 10:32 +0200
 
directory recursion (9 replies — unroll) "muta...@gmail.com" <mutazilah@gmail.com> 2022-08-16 03:01 -0700
   → Re: directory recursion "R.Wieser" <address@not.available> 2022-08-16 15:08 +0200
     → Re: directory recursion "muta...@gmail.com" <mutazilah@gmail.com> 2022-08-16 13:35 -0700
       → Re: directory recursion "R.Wieser" <address@not.available> 2022-08-17 08:35 +0200
         → Re: directory recursion "muta...@gmail.com" <mutazilah@gmail.com> 2022-08-18 01:24 -0700
           → Re: directory recursion "R.Wieser" <address@not.available> 2022-08-18 12:06 +0200
             → Re: directory recursion "muta...@gmail.com" <mutazilah@gmail.com> 2022-08-19 00:38 -0700
               → Re: directory recursion "R.Wieser" <address@not.available> 2022-08-19 13:08 +0200
                 → Re: directory recursion "muta...@gmail.com" <mutazilah@gmail.com> 2022-08-20 03:55 -0700
   → Re: directory recursion Steve Nickolas <usotsuki@buric.co> 2022-08-16 13:59 -0400
 
is there a high-frequency timer available on the PC? (besides the PIT) (5 replies — unroll) Mateusz Viste <mateusz@xyz.invalid> 2022-08-17 12:01 +0200
   → Re: is there a high-frequency timer available on the PC? (besides the PIT) Johann Klammer <klammerj@NOSPAM.a1.net> 2022-08-17 19:02 +0200
   → Re: is there a high-frequency timer available on the PC? (besides the PIT) rridge@csclub.uwaterloo.ca (Ross Ridge) 2022-08-19 15:25 +0000
     → Re: is there a high-frequency timer available on the PC? (besides the PIT) rridge@csclub.uwaterloo.ca (Ross Ridge) 2022-08-19 19:44 +0000
       → Re: is there a high-frequency timer available on the PC? (besides the PIT) Mateusz Viste <mateusz@xyz.invalid> 2022-08-19 22:16 +0200
         → Re: is there a high-frequency timer available on the PC? (besides the PIT) "Alexei A. Frounze" <alexfrunews@gmail.com> 2022-08-19 21:20 -0700
 
A comment on DOSLITE and COMMAND.COM (1 reply — unroll) Steve Nickolas <usotsuki@buric.co> 2022-08-02 09:28 -0400
   → Re: A comment on DOSLITE and COMMAND.COM Robert Riebisch <Robert.Riebisch@arcor.de> 2022-08-07 21:54 +0200
 
A spreadsheet called 'The Cracker' (9 replies — unroll) roger <techfell@gmail.com> 2021-06-18 04:44 -0700
   → Re: A spreadsheet called 'The Cracker' "R.Wieser" <address@not.available> 2021-06-18 14:27 +0200
     → Re: A spreadsheet called 'The Cracker' roger <techfell@gmail.com> 2021-06-18 06:08 -0700
       → Re: A spreadsheet called 'The Cracker' "R.Wieser" <address@not.available> 2021-06-18 15:35 +0200
   → Re: A spreadsheet called 'The Cracker' Sjouke Burry <burrynulnulfour@ppllaanneett.nnll> 2021-06-19 03:05 +0200
     → Re: A spreadsheet called 'The Cracker' JJ <jj4public@gmail.com> 2021-06-19 20:35 +0700
       → Re: A spreadsheet called 'The Cracker' "muta...@gmail.com" <mutazilah@gmail.com> 2021-06-19 12:36 -0700
   → Re: A spreadsheet called 'The Cracker' Rube Longfellow <rube@uselessbastard.net> 2021-10-22 10:29 +0000
   → Re: A spreadsheet called 'The Cracker' Anon Ymous <iownertoday@gmail.com> 2022-07-13 12:35 -0700
     → Re: A spreadsheet called 'The Cracker' "Kerr-Mudd, John" <admin@127.0.0.1> 2022-07-14 21:21 +0100
 
Print to PDF on DOS Ben Collver <bencollver@tilde.pink> 2022-06-16 02:49 +0000
 
show current Month's calendar in 256 bytes (6 replies — unroll) "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2022-05-11 11:11 +0100
   → Re: show current Month's calendar in 256 bytes "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2022-05-13 14:45 +0100
     → Re: show current Month's calendar in 256 bytes "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2022-05-14 09:25 +0100
       → Re: show current Month's calendar in 256 bytes Frank Kotler <fbkotler@nospicedham.myfairpoint.net> 2022-05-14 20:10 -0400
       → Re: show current Month's calendar in 256 bytes Frank Kotler <fbkotler@nospicedham.myfairpoint.net> 2022-05-14 20:19 -0400
       → Re: show current Month's calendar in 256 bytes "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2022-05-16 17:15 +0100
         → Re: show current Month's calendar in 256 bytes "Kerr-Mudd, John" <admin@nospicedham.127.0.0.1> 2022-05-17 08:03 +0100
 
Wordle for DOS in 250 bytes "Kerr-Mudd, John" <admin@127.0.0.1> 2022-04-28 13:49 +0100
 
PDOS/86 "muta...@gmail.com" <mutazilah@gmail.com> 2022-04-21 18:46 -0700
 
Book source code, The Undocumented PC (5 replies — unroll) Trifle Menot <triflemenot@protocol.invalid> 2017-01-24 17:15 +0000
   → Re: Book source code, The Undocumented PC rugxulo@gmail.com 2017-01-24 12:27 -0800
     → Re: Book source code, The Undocumented PC Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> 2017-01-24 23:04 -0500
       → Re: Book source code, The Undocumented PC Trifle Menot <triflemenot@protocol.invalid> 2017-01-25 14:18 +0000
         → Re: Book source code, The Undocumented PC Mathieu Kacou <kacoumathieu@gmail.com> 2022-01-29 20:17 -0800
   → Re: Book source code, The Undocumented PC Bogus@Embarq.com (Steve) 2017-01-25 12:57 +0000
 
Re: I Need a millesecond Timer under DOS ? Game Corner Playthroughs <phasershow@gmail.com> 2021-12-21 12:08 -0800
 
ioctl (6 replies — unroll) "muta...@gmail.com" <mutazilah@gmail.com> 2021-12-06 18:59 -0800
   → Re: ioctl "R.Wieser" <address@not.available> 2021-12-07 10:39 +0100
     → Re: ioctl "muta...@gmail.com" <mutazilah@gmail.com> 2021-12-08 17:00 -0800
       → Re: ioctl "R.Wieser" <address@not.available> 2021-12-09 10:14 +0100
         → Re: ioctl "muta...@gmail.com" <mutazilah@gmail.com> 2021-12-09 06:51 -0800
           → Re: ioctl "R.Wieser" <address@not.available> 2021-12-09 17:14 +0100
             → Re: ioctl "muta...@gmail.com" <mutazilah@gmail.com> 2021-12-09 15:15 -0800
 
How to access stack-based data (strings) when SS <> DS ? (29 replies — unroll) "R.Wieser" <address@not.available> 2021-12-04 08:56 +0100
   → Re: How to access stack-based data (strings) when SS <> DS ? "Kerr-Mudd, John" <admin@127.0.0.1> 2021-12-04 12:47 +0000
     → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-04 15:57 +0100
       → Re: How to access stack-based data (strings) when SS <> DS ? "Kerr-Mudd, John" <admin@127.0.0.1> 2021-12-04 16:13 +0000
         → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-04 18:41 +0100
           → Re: How to access stack-based data (strings) when SS <> DS ? "Kerr-Mudd, John" <admin@127.0.0.1> 2021-12-04 20:28 +0000
             → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-05 08:56 +0100
               → Re: How to access stack-based data (strings) when SS <> DS ? "Kerr-Mudd, John" <admin@127.0.0.1> 2021-12-05 10:32 +0000
                 → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-05 13:11 +0100
                 → Re: How to access stack-based data (strings) when SS <> DS ? "Kerr-Mudd, John" <admin@127.0.0.1> 2021-12-05 12:21 +0000
                 → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-05 14:59 +0100
         → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-04 19:00 +0100
   → Re: How to access stack-based data (strings) when SS <> DS ? JJ <jj4public@gmail.com> 2021-12-05 14:27 +0700
     → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-05 12:43 +0100
   → Re: How to access stack-based data (strings) when SS <> DS ? "Alexei A. Frounze" <alexfrunews@gmail.com> 2021-12-05 22:25 -0800
     → Re: How to access stack-based data (strings) when SS <> DS ? Mateusz Viste <mateusz@xyz.invalid> 2021-12-06 09:30 +0100
     → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-06 14:33 +0100
       → Re: How to access stack-based data (strings) when SS <> DS ? Herbert Kleebauer <klee@unibwm.de> 2021-12-06 19:01 +0100
         → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-06 21:16 +0100
           → Re: How to access stack-based data (strings) when SS <> DS ? Herbert Kleebauer <klee@unibwm.de> 2021-12-07 00:19 +0100
             → Re: How to access stack-based data (strings) when SS <> DS ? Mateusz Viste <mateusz@xyz.invalid> 2021-12-07 09:31 +0100
             → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-07 09:37 +0100
             → Re: How to access stack-based data (strings) when SS <> DS ? Newbie language. "R.Wieser" <address@not.available> 2021-12-08 10:16 +0100
               → Re: How to access stack-based data (strings) when SS <> DS ? Newbie language. Herbert Kleebauer <klee@unibwm.de> 2021-12-08 17:39 +0100
                 → Re: How to access stack-based data (strings) when SS <> DS ? Newbie language. "Kerr-Mudd, John" <admin@127.0.0.1> 2021-12-08 17:37 +0000
                 → Re: How to access stack-based data (strings) when SS <> DS ? Newbie language. Herbert Kleebauer <klee@unibwm.de> 2021-12-08 22:31 +0100
                 → Re: How to access stack-based data (strings) when SS <> DS ? Newbie language. "Kerr-Mudd, John" <admin@127.0.0.1> 2021-12-09 21:43 +0000
                 → Re: How to access stack-based data (strings) when SS <> DS ? Newbie language. "R.Wieser" <address@not.available> 2021-12-08 22:19 +0100
       → Re: How to access stack-based data (strings) when SS <> DS ? "Alexei A. Frounze" <alexfrunews@gmail.com> 2021-12-06 22:40 -0800
         → Re: How to access stack-based data (strings) when SS <> DS ? "R.Wieser" <address@not.available> 2021-12-07 10:17 +0100

← Newer ~Page 1 of ~14 (articles 4141–4286) Older →


csiph-web