HDTenEightyP/NetNews huggingface dataset:
From: pynq@quads.uchicago.edu (Jeremy Mathers)
Subject: Re: where should SET name=thing go?
Reply-To: pynq@midway.uchicago.edu
Organization: D. J. Dougherty & Associates
Date: Mon, 14 Dec 1992 15:18:47 GMT

In article <1992Dec14.065220.19796@cdf.toronto.edu> g1nickut@cdf.toronto.edu (Nick Zahariadis) writes:
...
> Just to pull the rug from under your feet, OS/2 does NOT use the
> 'Autoexec.Bat' file AT ALL. Go ahead and move it to a floppy; OS/2 will
> still boot its merry way into your system.
>
> The 'Autoexec.Bat' is there for DOS sessions only. Therefore the 'SET'

The tricky part of this, as I indicated in another post, is that
AUTOEXEC.BAT gets runs for *all* simulated DOS sessions (but not for
"specific DOS"), which means that when you launch a DOS program from
within a OS/2 session, the window that gets launched runs AUTOEXEC.
I think it also gets run when you launch a WIN/OS2 session, but I am not
sure - I read something somewhere that indicated you could not have
anything that paused for input in AUTOEXEC.BAT if you were using WIN/OS2.

This presents a problem for those of us who are used to having long,
involved AUTOEXECs (mine are usually several screens long, and involving
much environment testing/looping/asking questions.  There needs to be
a way to do this stuff only when you are spawning an interactive DOS
session; otherwise you want to have a streamlined AUTOEXEC that
basically contains only SET statements.  It turns out that OS/2 goes out
of its way to make this difficult.  It is nothing short of diabolical.

After much playing, I found a way to do it.  (You'll love this!)
In your notebook for the interactive DOS session Icon, you put /E:1024
in the Parameters box.  What this does is set the env size to 1024 only
for the interactive sessions.  Now all you have to do is be able to
detect this fact in the AUTOEXEC.BAT.  I had written, some time back, a
program called READVAR (freeware availble upon request) that, among
other things, can tell you how large your environment is.  When run with
no args, READVAR will write a brief usage msg to stdout, including a
display of the current env size.  Thus, my AUTOEXEC contains the
following:

	readvar | grep 1024 >nul
	if errorlevel 1 goto not_interactive_shell
	...	(interactive shell stuff here)

Pretty cool, eh?

************************************************************************
Swipple's Rule of Order:
	He who shouts the loudest has the floor.

	- pynq@quads.uchicago.edu, who is still costing the net
	  hundreds, if not thousands, of dollars, every time he posts -
************************************************************************
From: bdubbs@cs.tamu.edu (Bruce Dubbs)
Newsgroups: comp.os.os2.misc
Subject: Re: Which Tape Drive for OS/2?
Date: 19 Dec 1992 16:46:37 GMT
Organization: Computer Science Department, Texas A&M University
NNTP-Posting-Host: neuron.tamu.edu

In article <1992Dec17.231529.23670@a.cs.okstate.edu> teague@a.cs.okstate.edu (Keith Teague) writes:
>Does anybody have any further info on getting the Irwin Accutrac drive and
>EZtape for PM to work with the latest (GA+CSD) release of OS/2. It fails
>to operate correctly for me using either the latest beta (11/92 PDK) and
>the GA+CSD release of OS/2. A call to Irwin just confirmed that they
>were aware of the problems but that they had no idea when/if there would
>be a fix available - they don't even understand the problem yet, they
>told me! By the way, I am using the 4100c interface board, not the
>floppy controller to run the drive.
>
>Does any one know of other software that will work with the Irwin
>Accutrac drives? Maybe that is an option.
>
I'm using EZtape for PM & the Accutrac 250 drive with the floppy
controller. It seems to work correctly for me.  I did have a minor
problem with the .ini file but when it was deleted, the system created
a new one correctly.
   -- Bruce



--
Bruce Dubbs                   |  Oxymorons of note:
bdubbs@neuron.tamu.edu        |  Honest Politician, Political Science,
                              |  Scrupulous Lawyer
Newsgroups: comp.os.os2.misc
From: wkn@leland.Stanford.EDU (Ken Neighbors)
Subject: VIDEO_MODE_RESTRICTION slows down DOS box
Followup-To: comp.os.os2.misc
Keywords: VIDEO_MODE_RESTRICTION
Organization: DSG, Stanford University, CA 94305, USA
Date: Thu, 17 Dec 92 01:35:14 GMT

I thought I'd set VIDEO_MODE_RESTRICTION to CGA so that I could get
96K more of memory for one of my text only DOS apps.  It now runs
twice as slow (or half as fast :)

Here's some data:
restriction	mem		time to run
NONE		655360		16 seconds
CGA		753664		33 seconds
MONO		720896		33 seconds

There's no mention that these settings will slow down the system.
I've got a 486/33, and I'm running the win3.1+32GRE beta.

Hmmm.  I was supposed to "destroy" my copy yesterday.  I don't know
if it would have been this slow before yesterday, maybe I'll set the
computer date back a couple days and see :) :)

Ken Neighbors
wkn@leland.stanford.edu
From: bert.tyler@satalink.com (Bert Tyler)
Newsgroups: comp.os.os2.misc
Subject: Re: Why not standard VESA
Date: 20 Dec 92 12:48:00 GMT
Reply-To: bert.tyler@satalink.com (Bert Tyler)
Organization: Datamax/Satalink Connection * Ivyland, PA (215) 443-9434

<>>   b. VESA is useless in facilitating background execution of DOS programs.
<>>      So, with a VESA driver, DOS background execution could not be allowed.

OK, this item is back on the topic of OS/2, so I feel better about
pursuing it.

What exactly (other than inertia) prevents OS/2 from providing VESA
support for the background execution of DOS programs?  The "real mode"
VESA VBE is just an extension of the INT 10H video BIOS, and involves
no hardware extensions at all.  In fact, all it really involves is
support for a larger virtual video space and bank-switching.  Support
for the VESA 800x600x16 mode doesn't even involve that.  Given the
tremendous amount of effort that must have gone into the virtual VGA
support for background execution of DOS programs, these two items
seem rather trivial (of course, I'm not the one who would have to do
it, which is undoubtedly clouding my judgment <grin>).

The OS/2 "DOS Box" code fully implements the INT 10H BIOS.  Given that
an OS/2 SuperVGA video driver has to know all about throwing its
underlying adapter into and out of its various SuperVGA video modes
(otherwise, it couldn't support full-screen VGA DOS sessions as well
as a SuperVGA OS/2 desktop), what prevents the DOS Box code from
adding selected VESA modes as well?  It's actually using the true
spirit of OS/2, hiding the ugly details of the real hardware from the
application program.  It's also a lot easier than supporting any
"real" DOS-mode access to the video hardware's SuperVGA capabilities.

(There *is* one penalty for adding any SuperVGA video support at all
to DOS boxes - once you've added support for a video mode that requires
512K or 1MB of video RAM, you *have* to save and restore that video
RAM every time you switch to and from that DOS session.  That's not
a problem unique to VESA support, though.)

                   Bert Tyler   (bert.tyler@satalink.com)
---
 . DeLuxe./386 1.25 #343sa . Did you expect mere proof to sway my opinion?
                                                                  
Newsgroups: comp.os.os2.misc
From: Steve.Withers@bbs.actrix.gen.nz
Subject: Re: 32-bit Trident Drivers!
Organization: Actrix Information Exchange
Date: Mon, 14 Dec 1992 09:10:26 GMT

In article <1992Dec10.190938.1136764@sue.cc.uregina.ca> skagos@hercules.cs.uregina.ca (P. Takis Skagos) writes:
> In article <4DEC199215155715@vmsa.is.csupomona.edu> cvafyaga@vmsa.is.csupomona.edu (Srikanth Viswanathan) writes:
> >>  Apparently there are now 32 bit 256 color TVGA drivers on OS/2
> >> 
> >>/pub/uploads/trident32bit.exe
> >
> >But how do I install them though??!  The INSTALL.TXT is very sketchy,
> >and unlike the other Trident files,  this doesn't have a replacement
> >for the DISPLAY.DLL file.  Can ANYONE help?
> 
> 
> Whoever put this archive together really did a bad job.  The documentation
> sucks, the fact that it is a self-extracting DOS file sucks, the fact that
> it doesn't extract the subdirectories it should also really sucks.  Anyway,
> here's an explanation.

A corrected archive and documentation are on Hobbes and have been since
December 9th. The Tri32new.exe file contains updated documentation and a
re-packaged archive. 
 
I have deleted the original - which I had nothing to do with.
 
The doucmentation alone can be obtained by ftping the file Tri32new.txt.
 
These files are still not as nice as they could be....but I was home sick that
day and had only limited time to re-package it. 
 
Most people seem to have little difficulty getting the updated version to work
- provided they read the documentation before they start installing the
drivers.
 
Steve
-- 
Steve Withers - Wellington, New Zealand | On Sept. 19th, 88% of NZ voters opted
Steve.Withers@bbs.actrix.gen.nz         | for proportional representation. It
withers_s@kosmos.wcc.govt.nz            | looks like we may get a more  
**** Happy user of OS/2 v2!! ****       | democratic system "real soon now".
Newsgroups: comp.os.os2.misc
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: Are there any OS/2 Discussion Lists (Listserv)?
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Tue, 15 Dec 1992 20:31:54 GMT

In article <6109@sumax.seattleu.edu> limpe@sumax.seattleu.edu (Philipp Enrique T. Lim) writes:
>[Nothing.]

This question is answered in the FAQ List.

-- 
Timothy F. Sipples      | Read the OS/2 FAQ List 2.0h, available from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
Dept. of Econ., Univ.   | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637       | [Read the List, THEN post to ONE OS/2 newsgroup.]
From: lowey@jester.usask.ca (Stress Warlock)
Newsgroups: comp.os.os2.misc
Subject: Re: 32-Bit Trident Driver Installation (Repost)
Date: 13 Dec 92 20:36:10 GMT
Organization: University of Saskatchewan
NNTP-Posting-Host: jester.usask.ca
X-Newsreader: TIN [version 1.1 PL7]

Erik Kovach (enk2@po.cwru.edu) wrote:

: 3) Replace the old svga.exe with the new one.  Run "svga on dos"  That
: will create a file called svgadata.dos.  Note that the old svgadata.pmi
: and this svgadata.dos are in fact different, so you do have to replace
: it.

Remember to do this step from a DOS Full-screen session, or better yet,
boot up under DOS and run it without OS/2 loaded at all.  DO NOT do it from
an OS/2 VIO session, or from a DOS session running in a window.

: 5) Replace BVHSVGA.DLL with the new one.  (Note that I didn't replace
: vsvga.sys)

And this is important.  DO NOT INSTALL THE VSVGA.SYS FROM THE NEW DRIVERS.

: 6) Replace IBMDEV32.DLL with the appropriate one from the Trident 32-bit
: drivers.  When I extracted the drivers, they didn't go into separate
: directories (like it says in install.txt).  So, when I extracted them,
: the first one is for 640x480x256, the second one is 800x600x256 and the
: last is 1024x768x256.

It may uninstall correctly if you type "-d" after the program to do
the extraction, for example "tri32new -d"

For convenience, I've repackaged this as a ZOO 2.1 archive, so the proper
directories will be created when it is unpacked.  It is available on our
FTP site as /pub/archives/os2/drivers/tri32new.zoo

: 8) Type install.  That will run the install script to install the fonts.
:  Or, do it manually and replace the fonts like it says in install.txt.

This has to be done from the fonts subdirectory, if you extracted it with
the directories.  It also assumes that your /OS2/DLL directory is on drive C:

: 9) Rename svgadata.dos to svgadata.pmi.

Make sure this is in the /OS2 directory.

Finally, and most important, this MUST be done to OS/2 2.0 GA + the Service
Pack.  It won't work if you haven't installed the service pack.  To check
this, type SYSLEVEL.  It should say:

IBM OS/2 Base Operating System
Version 2.00     Component ID 562107701
Type 0
Current CSD level: XR06055
Prior   CSD level: XR02000

- Kevin Lowey (Lowey@Sask.USask.CA)
>>>>> Anonymous FTP to FTP.USASK.CA for DOS, OS/2, and Windows programs <<<<<
Newsgroups: comp.os.os2.misc
From: shurr@cbnews.cb.att.com (larry.a.shurr)
Subject: SWAPPER>DAT shrinking is a nuisance (was: ...reclaim my swap file?)
Organization: AT&T Bell Laboratories, Columbus, OH
Date: Tue, 15 Dec 1992 18:18:38 GMT

In article <sal8.240.724187146@po.cwru.edu> sal8@po.cwru.edu (Steve Luzynski) writes:
>In article <APOULSEN.92Dec11000207@marinara.mit.edu> apoulsen@athena.mit.edu (Andy Poulsen) writes:
>>From: apoulsen@athena.mit.edu (Andy Poulsen)
>>Subject: how can I tell what's swapped out and reclaim my swap file?

>>[Swapfile has grown to 15M and won't shrink].

>When you shutdown and restart the machine it should shrink back down. It 
>will sometimes shrink all on its own if you just let the machine sit for a 
>while...as long as there are no non-OS2 processes running. My machine stays 
>on all the time (last powerup was 4 months ago) and the swapfile is usually 
>back down to 4M in the morning...

Before I tweaked my settings to eliminate shrinking, I found that I only
had to let my machine stand idle for a few minutes and it would wake up
and shrink the swap file.  I have my swapfile in its own partition on
drive 2 so it's pretty easy to see paging activity.  When drive 2's light
flashes, it's usually paging or swapfile maintenance..

I eliminated shrinking by setting my swapfile size to 15360K as my swap
partition is 16M.  This is the largest setting I could get to work in
that paritition.  If OS/2 thinks your setting is too large, it appears
to use a default of 2048K.

I chose a non-shrinking swapfile because I found that the system was
fairly unresponsive during the shrink operation.  The mouse cursor seems
to move around OK (though I haven't tried it in some time with shrinking
enabled), but it doesn't respond to mouse clicks very well -- seems as
though the shrink operation must complete before it responds.  I realize
that I/O can only occur on one of the two disks at a time, and it may be
that the shrink operation must be completed once started before 
swapper.dat can be used again.

My controller is a venerable WD1007A which seems to be supported without
resorting to the INT13 driver so I've been assuming that it gives priority
to the shrink operation because the page management code thinks it should
rather than because the hardware requires it.  If I'm wrong, I'd like to
learn otherwise, peferable without flamage.

Larry
-- 
Larry A. Shurr (las@cbnmva.att.com) speaking only for myself.
Norman, listen carefully.  I am lying.  Are you sure your circuits are
registering?  Your ears are green.  Logic is a little bird singing in a
meadow.  Logic is a wreath of pretty flowers which smell bad! - Mr. Spock
From: h198@hosp.med.umich.edu  (Gene Mangum)
Newsgroups: comp.os.os2.misc
Subject: Re: Creative Labs CD-ROM problem.
Date: Tue, 15 Dec 1992  10:33 EDT
Organization: Univ of Michigan Hospitals
Distribution: world
NNTP-Posting-Host: condor.hosp.med.umich.edu
X-Newsreader: FTPNuz (DOS) v1.0

In Article <Bz9o0J.243G@austin.ibm.com> "tomg@rpc.austin.ibm.com (Tom Gardner)" says:
  
  [Stuff Deleted]
 
> I cannot access my CD-ROM using the driver provided by Creative Labs
> because I don't have MMPM/2 installed.  I have MMPM/2 ready to be installed
> but I have it on CD !!   So, what is a guy to do?  Is there any driver
> available for the Matsushita model 521-CAC that runs under os2 only
> (meaning without MMPM/2) or am I stuck?
  
  [Stuff Deleted]
 
  The CD driver is independent of MMPM/2.   You can use it by itself.
  Put the DEVICE= for it at the TOP of CONFIG.SYS (maybe after HPFS).
  There is some non-MMPM stuff for the SB board as well.
Newsgroups: comp.os.os2.misc
From: nap42487@uxa.cso.uiuc.edu (Nishith A. Patel)
Subject: Re: Trap 000C HEEELLLPPPP!
Organization: University of Illinois at Urbana
Date: Thu, 17 Dec 1992 05:33:04 GMT

ericwolf@mentor.cc.purdue.edu (Eric Wolf) writes:

>In the middle of playing Mike Ditka's football game in a full-screen
>DOS session, I got an error.  Well, it forced me to do a hard reset and
>then when I selected OS/2 from the boot manager, it started to boot up
>OS/2 and then it came up trap 000c - blah blah blah ( lots of register
>info and it told me to contact a service rep.)

>Well, I rebooted and again it said this again.  So, I tried to boot off the
>floppies and I got past the first disk (installation disk) and then I got 1/2
>way thru the 2nd one or so (disk #1) when it said that it could not open CON:
>and it could not continue without it.

Did you only try bpotting off the hard drive twice? I would try to do it more
often; I frequently have to boot three times to get it to actually boot without
a trap 0002 (and wait through that "chkdsk corrected allocation error" junk).
don't know if trap 000c, though.


>- Eric
From: gershon@husc11.harvard.edu (Ethan Gershon)
Newsgroups: comp.os.os2.misc
Subject: Re: OS/2 Western Digital drivers
Date: 13 Dec 92 22:57:39 GMT

gordon@galisant.demon.co.uk (Gordon Beck) writes:

>Anyone know if there are any SVGA drivers for the WD SVGA card, or
>know the WD BBS number?

In the U.S.:
Western Digital support number: 800-832-4778
WD BBS: 714-753-1234
FAX (I think): 714-932-6294

note that the assembly number for your WD video card (needed to access
the BBS) is on the *internal side* of the metal mounting bracket on the end
of the card.

As far as I know, there are currently no WD video drivers.

                                             --Ethan Gershon
                                             gershon@husc.harvard.edu
Newsgroups: comp.os.os2.misc
From: mccall@mksol.dseg.ti.com (fred j mccall 575-3539)
Subject: Re: Adaptec AHA-1542B and large SCSI questions
Organization: Texas Instruments Inc
Date: Mon, 14 Dec 1992 23:48:40 GMT

In <1992Dec12.174722.407@weyrich.UUCP> orville%weyrich@uunet.uu.net (Orville R. Weyrich) writes:

>I tried to use the Adaptec BBS and couldn't get through, so maybe the
>net can help....

>I got an Adaptec AHA-1542B controller and want to use it with OS/2 2.0
>and a large SCSI disk. 

>My question is this: I have heard that SCSI disks larger than 1 Gb may
>not work properly without BIOS upgrades or special drivers. Is this true for
>OS/2? 

I don't know if this is a problem for OS/2 or not, but if it is there
is no fix for it.  The Adaptec PROM upgrade is for DOS ONLY.  The
drivers for OS/2 make assumptions about the head/platter translation
that the Adaptec controller is doing that would break if you updated
the PROMs.

-- 
"Insisting on perfect safety is for people who don't have the balls to live
 in the real world."   -- Mary Shafer, NASA Ames Dryden
------------------------------------------------------------------------------
Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
Newsgroups: comp.os.os2.misc
From: mjharris@nyx.cs.du.edu (Mike Harris)
Subject: Re: Help with dual monitor configuration
Keywords: os2 waffle 165
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Sat, 12 Dec 92 21:20:03 GMT

I received email telling me about the ecomon utility and I have downloaded
it for future use but I think my problem is different. See I can't even
install OS/2 and I believe it is because there is no support for the
hercules (MDA) adapter and OS2 thinks it sees a hardware compatibility
problem. If all you have is a monochrome (MDA) adapter is there anyway to
get OS2 up and running? I don't really care about fancy colors and with
Xmas coming....... Well you know. TIA



--
Mike Harris 			>>>>> In stereo where available <<<<< 
InterNet: mikeh@tenet.edu
Newsgroups: comp.os.os2.misc
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Subject: Re: Growing os2sys.ini file
Reply-To: sip1@midway.uchicago.edu
Organization: Dept. of Econ., Univ. of Chicago
Date: Sat, 12 Dec 1992 22:25:06 GMT

In article <42230@sdcc12.ucsd.edu> pvanmeur@sdcc3.ucsd.edu (Pim van Meurs) writes:
>Hi I am a regular and predictable victim of the growing os2sys.ini
>file. I use cpyini to reduce it to its regular 134k or so. But every
>time I run os2 for a while (1-2 days) os2sys.ini steadily grows to
>1-1.5Mbyte. NOw this is completely unacceptable. I don't
>ctrl-alt-del but use normal shutdowm. Something I noticed that I
>have 3 pmworkplace handles. Using inimaint I looked at them.
>PM_Worrkplace:ActiveHandles, Pm_workplace:handles0,
>Pm_workplace:Handles1 Pm_workplace:handles. The are 19k blocks
>filled with names of files I once had on my system. They include th
>sp compressed disks filenames and much more historically interesting
>data. I wonder if they are the cause of my misery. Maybe I should
>reinstall the original ini files. Where are they btw as my ini
>backups are also contaminated. Maybe IBM should address this problem
>as it renders os2 unworkable since I have only 2Mbyte left on my
>system partition. Help

It appears IBM has released an INI "clean up" utility of their own,
and there are many excellent freeware/shareware alternatives.  Check
ftp-os2.nmsu.edu.  (As always, these items are just released, and they
do take a few days to make it over to ftp-os2.  Check /pub/uploads as
well as the main index file /pub/os2/00Index.  I believe the IBM
utility has the filename gcini.zip, but, as I said, I just heard about
it.)

-- 
Timothy F. Sipples      | Read the OS/2 FAQ List 2.0h, available from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
Dept. of Econ., Univ.   | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637       | [Read the List, THEN post to ONE OS/2 newsgroup.]
Newsgroups: comp.os.os2.misc
From: jdecarlo@mitre.org (John DeCarlo)
Subject: Re: IBM won't accept Internet problem reports any more
Organization: MITRE Corporation, McLean  VA
Date: Tue, 15 Dec 1992 17:23:08 GMT

In article <1gilu6INNriv@agate.berkeley.edu>
 stanton@haas.berkeley.edu (Richard Stanton) writes:

>I just got a message telling me that to report bugs etc I must now have
>a valid Compuserve account. What a pain.

That's interesting.  I just had a little round of problem reporting mail 
with them from my Internet account last week.  Suppose I contributed to 
their costs enough on my own to cause them to stop?

Why don't they accept abbreviated versions of the problem reporting forms, 
then, to save themselves some money?

John DeCarlo, MITRE Corporation, McLean, VA--My views are my own
Fidonet:  1:109/131  Internet:  jdecarlo@mitre.org
Newsgroups: comp.os.os2.misc
From: nap42487@uxa.cso.uiuc.edu (Nishith A. Patel)
Subject: How to deinstall appletts?
Organization: University of Illinois at Urbana
Date: Sat, 12 Dec 1992 21:53:21 GMT

How do you deinstall all the games that come with OS/2, except for solitaire?
Better yet, does anyone know how to install the solitaire which comes with
Windows? Then I would just delete all the games.

Thanks for any pointers.
From: ASI509@DJUKFA11.BITNET
Newsgroups: comp.os.os2.misc
Subject: Re: OS/2 NOT 32 Bit?
Date: 17 Dec 92 10:27:13 GMT
Organization: Forschungszentrum Juelich

In article <1992Dec17.014016.14071@magnus.acs.ohio-state.edu>,
lotozo@magnus.acs.ohio-state.edu (William A Lotozo) says:
>
>I have heard some people claim that OS/2 is not a 32 bit operating system
>but actually a 16 bit os running a 32 bit os emulation.  Is this so?
>I thought that if anything it was a true 32 bit os with a 16 bit emulation
>for backwards compatability to os/2 1.x programs.

You are right and they are wrong. There are _some_ parts that are 16Bit. Though
the only one I know of was the old (GA Version) graphics engine. Since the
service pack it is 32Bit. OS/2 has the old APIs for 16 apps and perhaps the
texmode I/O functions are 16Bit code. But as I understand IBM wants to move
to PM-only operation, so it would be logical not to change that to 32Bit code.

If it was a 16Bit OS, how could such things like the 32Bit GNU compilers exist
without an OS/2-extender like the DOS-extender version ?

Michael Bode.