HDTenEightyP/NetNews huggingface dataset:
From: leonard@qiclab.scn.rain.com (Leonard Erickson)
Subject: Re: Formatting problems with msdos 3.0
Reply-To: 70465.203@compuserve.com
Organization: SCN Research/Qic Laboratories of Tigard, Oregon.
Distribution: comp
Date: Tue, 7 Apr 1992 05:12:46 GMT

kgeikelb@baht.cs.ruu.nl (Klaas Eikelboom) writes:

>I have at my home a commedore PC-10 XT (that I use for wordprocessing) with
>the commedore's MS-Dos 2.11. Now I want to use a program that runs with
>MS-DOS 3.0 and later versions. So I wanted to upgrade my system with IBM's
>PC-DOS 3.10. Someone told me that later versions would put a too heavy load
>on the XT's 8088 processor. But when I want to format the fixed disk with
>the FORMAT of MS-DOS 3.10 the format fails. Now I had the next questions:

To go from MS-DOS 2.x to 3.x or later on a hard drive, first back up the drive
*Don't* use MS-DOS's BACKUP program! I'd recomend FASTBACK Plus...

Once you've backed up and verified that the backup is good, then use
your DOS 2.11 FDISK program to *remove* the partion(s) on the hard drive.
Then boot from your DOS 3.0 disk (actually, I'd recommend 3.30 or 3.31).
Use the DOS 3.xx FDISK to create a new partion (or partitions).

At this point you can do a FORMAT C: /S to format the hard drive. Install
DOS and restore from your backups... 


-- 
Leonard Erickson		      leonard@qiclab.scn.rain.com
CIS: [70465,203]			 70465.203@compuserve.com
FIDO:   1:105/56	 Leonard.Erickson@f56.n105.z1.fidonet.org
(The CIS address is checked daily. The others infrequently)
Newsgroups: comp.os.msdos.misc
From: adingus@magnus.acs.ohio-state.edu (Aaron T Dingus)
Subject: Help w/ Joystick Programming
Organization: The Ohio State University
Date: Thu, 16 Apr 1992 23:23:09 GMT

I could use a little help.  :-)

I have a TANDY 1000EX i8088, and I am trying to
recieve data from the built-in joysticks.

I know that they work on some games I have, so the
operating system, or BIOS, must have some way of
communicating with them.

Does anyone out there know what DOS/BIOS interrupts
or function calls and what registers must be sent and
recieved for me to recieve data from the joysticks and
buttons?

Any help would be appreciated.

Thanks.

-ATD
-- 
Aaron T. Dingus
Professional Athelete
The Ohio State Univeristy
adingus@magnus.acs.ohio-state.edu
From: ry01@ns1.cc.lehigh.edu (ROBERT YUNG)
Newsgroups: comp.os.msdos.misc
Subject: Help on 4DOS please...
Date: 10 Apr 92 16:41:33 GMT
Organization: Lehigh University

Look in the latest Pc-mag and you'll see an article on 4dos. A side picture
shows a list of files with certain files in color based on their extension.
Anybody know how to do this? Thanks!!!!
-- 
 (%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%)
  |  Off-campus address...                                          |
  |     first alley down this street, left refrigerator box. :-)    |
  |                                                                 |
   \_________Bobby Yung_______RY01@Lehigh.Edu________X-0471________/
Newsgroups: comp.os.msdos.misc
From: wanderer@athena.mit.edu (Opus)
Subject: Re: OS/2 2.0 Question
Organization: Massachusetts Institute of Technology
Date: Thu, 16 Apr 1992 07:57:34 GMT

I think the minimum you need for os/2, *without* dos and windows support,
is 15 megs.. if you want the dos and windows, it will take up 30... I
wouldn't bother trying it on a 40 meg hard drive....
From: psb@matt.ksu.ksu.edu (Jr Phillip S Buckland)
Newsgroups: comp.os.msdos.misc
Subject: Re: Error while running at 33 Mhz
Date: 16 Apr 1992 10:35:39 -0500
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

MDS128@psuvm.psu.edu writes:

>I've been having a problem running at 33 Mhz but not at 16 Mhz on my 386.
>I have a "Turbo" button that activates the 33Mhz mode, and whenever I
>switch to this mode, the computer locks.  In this mode, the computer
>won't even boot.  One hint:  the Turbo light stays faintly on in 16 Mhz
>mode - might this mean something?

	An initial suggestion would be to check the CMOS setup to see how
	many wait states are being used for memory accesses.  At 33MHz,
	70ns DRAMs require 1 wait state (or they do with the 486 I looked at
	yesterday! :-).  At 16MHz, *no* wait states would be required.

	You don't say how long you've had your system, nor whether you have
	recently added hardware to it.  If your system is under warranty, it
	is a problem for the vendor to resolve.  If not under warranty, it is
	your problem.  The symptoms imply inability to access RAM or I/O
	channel adapter cards (serial, parallel, video, etc.).  If you have
	recently added something to your system, try running at 33MHz with the
	added hardware removed.  Also, most CMOS setups permit you to specify
	the number of wait states for I/O channel access - I don't know what
	you should set this to, but you might try making the wait states the
	maximum the setup permits, then work back to the lowest number of wait
	states your machine will work with at 33MHz.

>This problem was intermittent for about 2 days, and now it's constant.

	Since it was intermittent first, it leads me to suspect a hardware
	problem rather than a setup problem.  However, upping the wait states
	used for RAM and I/O access may still provide a workable solution.

[deletions]

	Good luck.


We read the world wrong		| Phil Buckland
and say that it deceives us.	| psb@eece.ksu.edu
Tagore, from Stray Birds	| psb@matt.ksu.ksu.edu
Newsgroups: comp.os.msdos.misc
From: rlarson2@uxh.cso.uiuc.edu (Bob Larson)
Subject: Re: Help on 4DOS please...
Organization: University of Illinois at Urbana
Date: Fri, 10 Apr 1992 20:29:36 GMT

In <1992Apr10.164133.49181@ns1.cc.lehigh.edu> ry01@ns1.cc.lehigh.edu (ROBERT YUNG) writes:

>Look in the latest Pc-mag and you'll see an article on 4dos. A side picture
>shows a list of files with certain files in color based on their extension.
>Anybody know how to do this? Thanks!!!!
>-- 
There is an environment variable called colordir which controls this.
It's expained in the 4dos help listing for dir.


----------------------
Bob Larson
blarson@uiuc.edu
From: rmhlie@cs.vu.nl (Lie RMH)
Newsgroups: comp.os.msdos.misc
Subject: Re: Force 360K drive to read 720K disks
Keywords: 360K to 720K disk drives
Date: 8 Apr 92 06:19:23 GMT

leonard@qiclab.scn.rain.com (Leonard Erickson) writes:

><	drivparm=/d:1 /f:2

>Ok, the problem is that *some* version of DOS 3.3 have a "bug" with the
>way DRIVPARM is handled. Try inserting one to three ctrl-A characters
>before the =. They may need to be after it. It's been a *long* time
>since I had to deal with this.
>-- 

I don't know it exactly but I thought it was ^.

Greetings Max
  
Xref: sparky comp.os.msdos.programmer:5289 alt.msdos.programmer:1130
From: kentiler@matt.ksu.ksu.edu (Kent Iler)
Newsgroups: comp.os.msdos.programmer,alt.msdos.programmer
Subject: program to send dial code to modem
Date: 9 Apr 1992 22:04:27 -0500
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

Hello,
  Is there a way to have a program dial a modem?  For example, I want
to dial 1-800-NEC-INFO, I want to create a program in which I can
just type NEC-INFO and the program will translate the letters to numbers
and transfer it to the modem.  Thanks.

Actual consulting call -"I have this disk         Kent P. Iler                  
   stuck in my drive and I tried to get           Mainframe consultant          
   it out with a fork but ... "                   Kansas State University       
Bitnet : kentiler@ksuvm,Internet : kentiler@ksuvm.ksu.edu                       
Newsgroups: comp.os.msdos.programmer
From: elia@monsoon.cs.odu.edu (Lee Elia)
Subject: Re: Source to UUENCODE / XXENCODE
Organization: Old Dominion University Dept. of CS, Norfolk VA
Date: Sun, 12 Apr 1992 21:08:39 GMT

In article <702781917.F00005@cloud.pub.uu.oz.au> hamish@cloud.pub.uu.oz.au (Hamish Moffatt) writes:
>Anyone got any source to UUENCODE (prefered) and XXENCODE (if handy)? If so,
>please mail it to me, or tell me where I can get it. FTP not available to me,
>sorry.
>
>
>Regards,
>Hamish
>
> * Origin: Cloud Nine, Melbourne, Australia. cloud.pub.uu.oz.au (3:635/552)

Me too.  If this is available by FTP, where?

Lee

-- 
"...Generally, by the time you are Real, most of your hair has been loved off, 
and your eyes drop out and you get loose in the joints and very shabby.  But 
these things don't matter at all, because once you are Real you can't be ugly, 
except to people who don't understand..."    --    the Skin Horse
Newsgroups: comp.os.msdos.programmer
From: valley@gsbsun.uchicago.edu (Doug Dougherty)
Subject: Re: DOS is dead.
Organization: University of Chicago Computing Organizations
Date: Thu, 16 Apr 1992 19:58:26 GMT

nelson@crynwr.com (Russell Nelson) writes:

>DOS is dead.  (At most) A year from now no one will be programming for MS-DOS.

Hasn't this been done already?

Fooey on cross-posters!
****************************************************************************
The Slug		valley@gsbsun.uchicago.edu

Fudd's First Law of Opposition:
	Push something hard enough and it will fall over.

(THis [sic] message should be assumed to have been smiley captioned for the
humor impaired)
From: jpacker@willamette.edu (Jason Packer)
Newsgroups: comp.os.msdos.programmer
Subject: Re: DOS is dead.
Date: 16 Apr 92 03:48:49 GMT
Article-I.D.: willamet.1992Apr16.034849.3801
Organization: Willamette University, Salem, OR

In article <703214134snx@crynwr.com> nelson@crynwr.com (Russell Nelson) writes:
>DOS is dead.  (At most) A year from now no one will be programming for MS-DOS.
...much ado about "real" OS(es) deleted...
>-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
>Crynwr Software            Crynwr Software sells packet driver support.
>11 Grant St.               315-268-1925 Voice
>Potsdam, NY 13676          315-268-9201 FAX

Is it just me?  Am I the only person who is generally satisfied with MS-DOS? 
I mean, granted, I don't do much in the way of real msdos programming, but DOS
does about everything I want it to do, in my life, and for my uses.  I was
glad to see an equal contempt for windows, however, since I'm a diehard C:\>
kinda guy.  Now, all totalled, I've not run into one thing I've wanted to do
in DOS that I couldn't do.  Maybe I'm too big a newbie to know what's what,
but I'm pretty happy with MS-DOS.

PS...if you feel the need, flame away...anything infantile will be ignored.
From: nlonginow@falcon.aamrl.wpafb.af.mil
Newsgroups: comp.os.msdos.programmer
Subject: Borland -> Zortech: Do it ?
Date: 10 Apr 92 17:41:32 GMT
Organization: USAF AL/CFH, WPAFB, Dayton, OH

I frequently run out of memory in my applications of Borland C++, and have
been thinking about going to a 32-bit Compiler, like Zortech. This, as
opposed to using Borland (or Microsoft) followed by a DOS Extender 
(like Pharlap). The problem with the DOS extender route is being unable to
make use of the excellent debugging tools provided by Borland (and
Microsoft) on the runtime code. I'd like to stay with a well rounded
development and debugging environment, but ...  ANy ideas of the 
Zortech product ? (C++, that is)

-- 
Nick Longinow
Armstrong Lab
Human Engineering division


"The opinions and views expressed here are strictly my own and do not 
necessarily reflect the official position of either the U.S. Air Force 
or its contractors. "  You should think otherwise ?
From: singlis@waikato.ac.nz
Newsgroups: comp.os.msdos.programmer
Subject: Detecting VGA retrace! HELP!
Date: 8 Apr 92 10:56:23 +1200
Organization: University of Waikato, Hamilton, New Zealand

Greetings all!

Can anyone tell me which interrupt/mem location I can check to see if the
raster is in a retrace, this is so I can perform "nice" palette adjustments
without a lot of flicker...

thanks in advance...

email: singlis@waikato.ac.nz
From: jas37876@uxa.cso.uiuc.edu (John A. Slagel)
Newsgroups: comp.os.msdos.programmer
Subject: Re: How can I silence a ^C interrupt?
Date: 14 Apr 92 21:03:13 GMT
Article-I.D.: ux1.1992Apr14.210313.21622
Organization: University of Illinois at Urbana

richardh@hpopd.pwd.hp.com (Richard Hancock) writes:

>/ hpopd:comp.os.msdos.programmer / halvers@procyon.crd.ge.com (peter c halverson) /  6:55 pm  Apr  9, 1992 /

>>I'm trying to use Borland's "ctrlbrk" function to handle ^C/^Break events
>>(setting a flag that another routine eventually notices), and it seems to
>>work as advertised, except that I can't seem to suppress the echo of
>>"^C<CR>" to the screen (which trashes the display).  Obviously there's some
>>chunk of code outside the default ^C handler which is doing this echoing
>>(the BIOS keystroke handler, maybe?), but I thought I'd check before trying
>>to hunt it down myself.  Any suggestions?

    An easy way to get rid of it is to locate the cursor at a 
    non-displayed location, like row 26 when you're not using it.
From: yates@a.chem.upenn.edu (John H. Yates)
Newsgroups: comp.os.msdos.programmer
Subject: read with noecho
Date: 8 Apr 92 00:34:53 GMT
Article-I.D.: netnews.73164
Organization: University of Pennsylvania
Originator: yates@a.chem.upenn.edu

I need to call a function or routine from Fortran
that will prompt the user for a password, not
echo it as it is typed, and return that password
to the calling program for checking.

Can anyone supply, or point me to such an example for
SGI IRIX for 4D hardware, or on a MS DOS 5.0 platform?
(I need to get this working on both).

I had this working on VAX/VMS with system sys$qio
calls coded in Fortran. I now need to port the code
to DOS and IRIX now, and just be done with it.

The called routine can be in Assembler, Fortran, or
C, it only needs to be called from my Fortran.

Thanks, John
yates@a.chem.upenn.edu
From: zmola@bert.eecs.uic.edu (Carl Zmola)
Newsgroups: comp.os.msdos.programmer
Subject: Re: MS-C 7 : no OS/2 support ?
Date: 13 Apr 92 16:14:55 GMT
Organization: University of Illinois at Chicago

melchers@Harpo.Chemie.FU-Berlin.DE (Bernd Melchers) writes:

>It seems to me, that Microsoft removed the support of OS/2.
>Can MS-C 6 create programs that run under  IBM OS/2 2.0 ??

	It can create dos programs, but has no support for real
OS/2 programming.  Zortech C++ does, and they might be offering
discounts on there product.  

	Does anyone know how Zortech's MS windows support is?  I'd hate
to have to use two compilers, but it seems that MSC v7 is the best for
windows work, and I'm not sure I'm going to be doing OS/2 work.

	Carl
Newsgroups: comp.os.msdos.programmer
From: rgb@hp835.mitek.com (Glynn Brooks)
Subject: Re: How to test for a key ALREADY pressed?
Organization: OpenConnect Systems
Date: Tue, 7 Apr 1992 12:41:52 GMT

When a key is pressed, it is stored in the keyboard buffer.  If you call
BIOS Int 16h, function 1 or 11, you will get back an indication of
whether a keystroke is available or not, and what the keystroke is.  The
keystroke remains in the buffer until Int 16h, function 0 or 10 is
executed.

So, yes, you can see if a particular keystroke is in the buffer.  If
there are multiple keystrokes there, you can only see the first one.
From: ronkanen@cc.helsinki.fi (Osmo Ronkanen)
Newsgroups: comp.os.msdos.programmer
Subject: Re: 386 SX Bug
Date: 16 Apr 92 20:26:33 GMT
Organization: University of Helsinki

In article <3544@cruzio.santa-cruz.ca.us>, aki@cruzio.santa-cruz.ca.us writes:
> 
> I was going through some of my old files and just happened to find a file
> describing a bug with the 386SX.  This particular problem is _not_ documented
> in any publication I could get my hands on,  so if there is anyone out there
> keeping track of Intel's bugs...  (BTW,  it was a pain to ID this problem,
> since all the debuggers would execute the command correctly.  I imagine
> trapped execution mode prevents the problem).  Description follows:
> 
> /************************************************************************
>   The followning INLINE code turned up a _BUG_ in the Intel 386 SX 16 MHz
>   ***********************************************************************/
>  
> /**************************************************************************
>    When the CPU gets to CALLing the hardcoded addr, it will not return.
>    It gets lost in never never land. It seems,  that the address is not
>    correctly stored to the target memory location with the MOV command.
>  
>    I solved the problem by adding some NOP statements between the MOV and
>    the CALL.
>  
>    Aki Korhonen, January 5th, 1992.
>  
>    PS. Check out PC-BENCH 1.4 and the soon-to-be-released PC-DIAG!
> ***************************************************************************/
>  
>   asm     mov ax, segm
>   asm     mov bx, 0
>   asm     mov di, offset offs_tavu
>   asm     mov cs:[di], bx
>   asm     inc di
>   asm     inc di
>   asm     mov cs:[di], ax
>  
>   asm     db 0x9A        /* CALL FAR, next two words are: OFFS, SEGM */
>   asm    offs_tavu:
>   asm     dw 0
>   asm     dw 0
> 
> 
> Aki.
> 
> PS.  I know the code looks terrible,  and don't ask me why I didn't use
> far pointers.  I always work worst after 3 AM.
> -- 
> /  Phone: 408-662 9664 Fax: 662 9676  |  "Aki" pronounced: Ah-Key. I know  \ 
> \  GENIE: A.KORHONEN  Home: /dev/nul  |  what I'm doing most of the time.  /

It's not a bug. 386 SX has a prefetch queue. I don't know the 
exact length of the queue but on 386 DX it is 16 bytes, so I would guess
that it's 16 bytes also on SX. The processor has already fetched the call
instruction when the code modifies itself, so the processor doesn't see
the modification.

The problem doesn't occur if there is at least 16 bytes between the MOV
and the CALL, so adding some NOP:s helps (at least on 386).


Osmo.
Newsgroups: comp.os.msdos.programmer
From: leonard@qiclab.scn.rain.com (Leonard Erickson)
Subject: Re: turning off NUMLOCK
Reply-To: 70465.203@compuserve.com
Organization: SCN Research/Qic Laboratories of Tigard, Oregon.
Date: Tue, 7 Apr 1992 23:57:44 GMT

jaf@jaflrn.UUCP (Jon Freivald) writes:

>mcalame@servant.West.Sun.COM (Matthew Calame - SE Sacramento) writes:

>> Does anyone know how a program can turn off the NUMLOCK key/light on a PC?

>I've got a program that turns num/scroll/caps on/off from the command
>line.  If you haven't received anything else, give a holler & I'll
>uuencode it and e-mail it.


Warning!

*Any* code to do this will only work on machines with AT compatible BIOS
code. XT BIOS code doesn't pass the staus change back to the keyboard.

In fact, the XT keyboard interface has no way to pass the status back!

I mention this from sad experience. Unless your code can *guarantee*
that it is running on an AT or better, don't try to change CapsLock
or NumLock. Doing so will screw up the keyboard state. And be aware
that there are some machines out there that support enhanched keyboards
in the BIOS, but *don't* support the status change (Tandy comes to mind...)

-- 
Leonard Erickson		      leonard@qiclab.scn.rain.com
CIS: [70465,203]			 70465.203@compuserve.com
FIDO:   1:105/56	 Leonard.Erickson@f56.n105.z1.fidonet.org
(The CIS address is checked daily. The others infrequently)
From: sumargoh@serss0.fiu.edu (H. Sumargo)
Newsgroups: comp.os.msdos.programmer
Subject: A Driver to Redirect LPT# to a Network Port
Keywords: Network
Date: 15 Apr 92 00:54:50 GMT
Organization: Florida International Univ.


I am looking for a device driver that will redirect any LPT# port to the network port such that if I print to the port, it will be redirected to a designated network printer.  Please send you response to sumargoh@serss0.fiu.edu

Thank you.
From: dobbs@cod.NOSC.MIL (Lynn Dobbs)
Newsgroups: comp.os.msdos.programmer
Subject: Re: 4Eh Find First File - 4Fh Find Next File
Date: 17 Apr 92 15:46:09 GMT
Organization: Naval Ocean Systems Center, San Diego

In article <1992Apr16.195437.18025@ux1.cso.uiuc.edu> phil@ux1.cso.uiuc.edu (Phil Howard) writes:
>I would like to know exactly what the:
>    4Eh Find First File
>    4Fh Find Next File
>MS-DOS function calls provide.  The FILEINFO structure only has room for a
>single file name component.
>

        EXPIRAMENTATION IS THE KEY TO LEARNING.
From your request, it doesn't sound like you have tried to use find first
to see what it provides. It's just a few lines of code. Go ahead, live
a little.
From: abakker@cs.vu.nl (Arno BAKKER)
Newsgroups: comp.os.msdos.programmer
Subject: Re: DOS is dead.
Date: 16 Apr 92 10:36:58 GMT
Organization: Dept. of Computer Science, Vrije Universiteit Amsterdam

In article <92107.002553JJJ101@psuvm.psu.edu> JJJ101@psuvm.psu.edu writes:
>CONCLUSION: DOS is not dead, and will not be for many years.
>James

But it should have been for many years, (no smiley here)


			Arno
From: ts@uwasa.fi (Timo Salmi)
Newsgroups: comp.os.msdos.programmer
Subject: Re: How to a print *really* big letters?
Date: 9 Apr 92 20:11:24 GMT
Organization: University of Vaasa, Finland

In article <phil.702787613@adam.adelaide.edu.au> phil@adam.adelaide.edu.au (Phil Kernick) writes:
>I need to be able to display a large character (one of the standard ASCII
>set) in the middle of a VGA display.
>This does not sound like it should be too difficult, but up to now, I have
>not been able to find a way to do it, without having to define all of the
>character set myself.
>I was hoping to be able to use TurboPascal6.0, but the font support is only
>vector, so while I can draw big characters, they are not solid - which I
>require for my application.
>I have already grepped through the simtel archive, and cannot find anything
>like this.

The fonts can be found at a certain memory location.  As far as I
can recall I have a pointer about it in my Frequently Asked
Questions Turbo Pascal section.

104992 Mar 16 13:25 garbo.uwasa.fi:/pc/ts/tsfaq27.zip

Also see (but no source available):

garbo.uwasa.fi:/pc/ts/tsdemo15.zip Demonstrations by Timo Salmi
Filename        Comment                             Date      Time  
--------        --------------------------------    ----      ----  
BIGCHAR.EXE     Draws large characters on screen  09-07-90  19:49:32
BIGTIME.EXE     Date and time in big characters   09-07-90  19:49:38
PLOTDEMO.EXE    (P)lots of different functions    08-19-88  07:41:08
TSDEMO.INF      Document                          09-08-91  08:40:06
TSDEMO.NWS      News announcements about tsdemo   09-08-91  08:23:30
TSPROG.INF      List of PD programs from T.Salmi  07-30-91  23:11:54
TURBDEMO.EXE    Turbo Pascal graphics demo        09-08-91  08:18:46
VAASA.INF       Info: Finland, Vaasa, U of Vaasa  02-02-90  11:52:54
----            ------             ------  -----
0008            159432             123454   23%

...................................................................
Prof. Timo Salmi
Moderating at garbo.uwasa.fi anonymous ftp archives 128.214.87.1
School of Business Studies, University of Vaasa, SF-65101, Finland
Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun
From: richardh@hpopd.pwd.hp.com (Richard Hancock)
Date: Thu, 16 Apr 1992 09:44:48 GMT
Subject: Re: DOS is dead.
Organization: The Duffer of St. George
Newsgroups: comp.os.msdos.programmer

/ hpopd:comp.os.msdos.programmer / nelson@crynwr.com (Russell Nelson) /  2:15 am  Apr 14, 1992 /

Reminds me of the old Nietzsche joke; to paraphrase :-

  "DOS is dead," Russell Nelson.
  "Russell Nelson is dead," DOS.

Or the old J.M.Keynes vs. proponents of classical economics joke; to
paraphrase :-

  "In the end we'll have a perfect OS," Dogmatists.
  "In the end we're all dead," Pragmatists.