HDTenEightyP/NetNews huggingface dataset:
Subject: Re: Port from WIN3.X -> WIN32 
Distribution: world
Organization: None
Reply-To: chris@chrism.demon.co.uk
X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
Date: Sat, 12 Dec 1992 18:32:23 +0000

In article <strobl.724160213@gmd.de> strobl@gmd.de writes:

>Howdy,
>General interest question.  
>       A - How is the port between WIN3.x -> WIN32 ?

>               1 - What types of changes are required ?
>               2 - Any personal Experiences ??
>
>
-- 

Probably the best way to start out the port of the code is:

1.   Set the STRICT flag and get the code to compile without warning
     messages on the /W3 level.

2.   Read the documentation for "windowsx.h" and start using the
     "message cracker" macros instead of the normal "switch" statement
     in your message loop.

When you've done these two things, and you can build your application for
Windows 3.1 without warnings. the port to Win32 should be a straighforward
process.


--------------------------------------------------------------------------
| Chris Marriott                   | chris@chrism.demon.co.uk            |
|                                  | BIX: cmarriott                      |
| (Still awaiting inspiration      | CIX: cmarriott                      |
|  for a witty .sig .... )         | Compuserve: 100113,1140             |
--------------------------------------------------------------------------
From: failsafe@cellar.org (Failsafe)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Fatal Error Install!
Date: 13 Dec 92 23:29:15 GMT
Organization: The Cellar BBS and public access system

It seems that I too have been hampered in installing NT. This with the
October (green) beta. Message and system details below.

error message= "Fatal System Error 0X00000077, I/O error on kernal stack
paging operation, kernal debugger using COM 2:"
This occurs during the graphical part of the installation on the fiel
srvsvc.dll (at 22% of installation) or resolver.dll (21%). It is
reproducible as well.

System:

AMI Ez-Flex Motherboard 486-33
16Mb memory
Ami Fast Disk SCSI controller (works as adaptec 1542 with DOS, OS/2 and
   recognized as such by NT, AMI technical support says it is hardware
   compatible and has used it with NT)
ATI VGA Wonder + with bus mouse (used in plain VGA mode) on IRQ 3
Texel CD-ROM DM-5024 -external SCSI add=4
Soundblaster Pro IRQ 5
Roland LAPC-1 IRQ 2/9
Archive Python DAT drive- external SCSI add=2
Two Micropolis SCSI HD's 1684 (330 MB) and 2112 (1005 Mb) as drive 1 & 2
   respectively

Could this be related to the standard IRQ for COM 2 being used by the mouse?

Also I get a message that EISA memory is inaccurately configured and that the
system would use ISA reports, but this doesn't seem to stop the install. It
reports that I have 16064 K of memory when in fact I have 16,000 K. Is this
the cause of the error message? Should I worry about this also? 

Thanks for any and all suggestions! 


----------------------------------------------------------------------------
Steve Roth                      The Cellar BBS (215) 654-9187
Philadelphia, PA.               No witty saying yet, maybe not ever!
Preferred Mailpath: cellar%failsafe@tredysvr.tredydev.unisys.com
Alternate mailpath: failsafe@cellar.org
From: tad@wrq.com (Tad Marshall)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Installation adveNTures with NT
Date: 18 Dec 92 22:46:20 GMT
Article-I.D.: u.1992Dec18.224620.23561
Organization: Walker Richer & Quinn, Inc., Seattle, WA

In article <1992Dec18.183132.9043@nsisrv.gsfc.nasa.gov> williams@nssdcs.gsfc.nasa.gov (Jim Williams) writes:
>I have an Adaptec 1542B SCSI controller and the CD-ROM is from one of
>our Silicon Graphics Indigos.  Its a Toshiba 3301.  Perhaps SGI
>tampers with the ROM in some way...?

From things I have read in alt.cdrom, I believe that this is true -- SGI has
made a few changes in the drive -- I don't remember what they are.  Sounds like
you got it to work anyway, though.

>So, my questions are:
>
>Any idea why my CD-ROM didn't work?

SGI modifications seem to be a likely culprit -- my CD Technology Porta-
Drive is also based on the Toshiba 3301, and it works fine with a 1542B.

>Does the ET4000 Tseng driver work at 1024x768?  Any ideas why I got a
>blank screen?

I don't know the Diamond SpeedStar 24, but I'm using the original Diamond
SpeedStar at 1024x768x16 with a NEC 4FG with no problems.  I think that the
NT driver runs the SpeedStar at a pretty aggressive refresh rate, but I'd
have thought that the NEC 4D could handle it.  You mentioned a 24-bit DAC --
perhaps that is the problem.

>How can I make an emergency repair disk manually?  What good is it?

As near as I can figure, the Emergency Repair Disk saves your original
registry so that you can revert to a working configuration.  I haven't had
to use one, so I don't know how well it works.  If NT is installed onto a
FAT partition, you can also rename the ET4000 driver to *.foo and NT will
revert to VGA on the next boot.

-- Tad
Newsgroups: comp.os.ms-windows.programmer.win32
From: johnhall@microsoft.com (John Hall)
Subject: Re: Can someone post how to ask Microsoft a question on Compuserve
Date: 16 Dec 92 18:08:07 GMT
Organization: Microsoft Corporation

In article <BzBCKy.Jp@unx.sas.com> sasdxk@skyhawk.unx.sas.com (Dave Kolb) writes:
| Really, they are trying some but I find CIS pretty frustrating.
| 
| Better would be WNT phone support and incident numbers and a list of
| known problems and solutions.
| 

For programming related questions, use mswin32.  End users and install
issues are in winnt.

There is now a 'bug list' of known bugs you can download.
The install section in winnt *may* have a FAQ, I don't remember.

-- 
-------------------------
My comments are my own.  They are independent and unrelated to the
views of my company , relatives or elected representatives.
From: drahnier@britti.first.gmd.de (Reinhard Rasche)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: ATI drivers for Ultra Plus/Pro at CICA
Date: 15 Dec 92 05:50:08 GMT
	<1992Dec13.135208.2902@brandonu.ca>
Organization: GMD-FIRST, Berlin
In-reply-to: goldsborough@brandonu.ca's message of 13 Dec 92 19:52:07 GMT

actually, the file has been repostet and currently can be found in the
uploads directory. it is called aunt03.zip or something like that. the
driver seems to be slow and requires the aperture to be enabled.
however, it works ...
/*
 *  Dr. Reinhard W. Rasche		GMD/FIRST
 *  email: drahnier@first.gmd.de	Rudower Chaussee 5
 *  voice: +49 30 6704 -2660, -4255     1199 Berlin Adlershof
 *  fax:   +49 30 6704 -5610
 */
--
/*
 *  Dr. Reinhard W. Rasche		GMD/FIRST
 *  email: drahnier@first.gmd.de	Rudower Chaussee 5
 *  voice: +49 30 6704 -2660, -4255     1199 Berlin Adlershof
 *  fax:   +49 30 6704 -5610
 */
Newsgroups: comp.os.ms-windows.programmer.win32
From: rdenton@encore.com (Roger Denton)
Subject: WANGTEK 5150ES driver needed
Organization: Encore Computer Corporation
Date: Tue, 15 Dec 1992 19:36:58 GMT
Summary: tape driver needed

I have a WANGTEK 5150ES tape drive in my NT development machine. This
tape drive is not on the list of hardware support by the NT pre-release.
 
Does anyone have (or know where I can get) a driver for this device?
The manufacturer of the drive (WANGTEK) and the computer (Alpine)
don't have a clue.
 
MICROSOFT:
        Please add this drive to your list of devices to be supported.
        Also, please acknowledge that you received this request.

Thanks,
	Roger Denton

roger@encore.com
From: msieber@csghsg5a.bitnet
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: What's sys.spccmosram ???
Date: 18 Dec 92 22:15:37 GMT
Organization: University of St.Gallen, Switzerland

After installing "IBM - Standard VGA", it's possible
to run DOS-Applications, but before, say "x-program"
runs, the following messagebox appears:

   An Installation file required by NTVDM is missing,
   execution must terminate.
   sys.spccmosram

   This may cause (x-program) to function incorrectly.
   Continue running or terminate the application

   CONTINUE     TERMINATE

After choosing CONTINUE (most) DOS-Apps seem to run.

But when starting a win16-Application, the same messagebox
appears (where "x-program" is replaced by "16-bit Windows-
Application"). But when clicking on CONTINUE, the application
seems to work for some moments, no window appears and then 
I'm back in Program-Manager (or CMD-Prompt).

I made a Express installation and there's no file
called "sys.spccmosram" at all. But there can't be:
since no FAT-Filename can be 3 Characters plus 10 Characters
Extension!

Has anybody got an idea, what sys.spccmosram could mean?

BTW: The Message comes (in case of a DOS-APP) from the
"16-Bit DOS-Subssystem" or (in case of a win16-APP) from the
"16-Bit Windows-Subsystem".

Thanks for every reply or letter.

	Martin Sieber

Newsgroups: comp.os.ms-windows.programmer.win32
From: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Subject: NT LAN-Manager Domain
News-Software: IBM OS/2 PM RN (NR/2) v0.16 by O. Vishnepolsky and R. Rogers
Reply-To: hochstae@allfiwib1.wiwi.uni-marburg.de (Christoph H. Hochstaetter)
Organization: Techn. Univ. Clausthal
Date: Mon, 14 Dec 1992 02:40:56 GMT

Does anyone know, how to change the Domain name in Lan Manager for NT?
Or more precisly on a primary Domain Controller of a NT domain.
The documentation says, that it is not possible to choose the domain
dialog from Network Setup in the Control Panel on Domain Controllers,
which is true indeed.
But what to do, if you want to change the name of your domain? (except
reinstalling NT from scratch)

Christoph
-------------------------------------------------------+-----------------------
Christoph H. Hochstaetter, Philipps-University Marburg | Universitaetsstr. 25
Internet: hochstae@allfiwib1.wiwi.uni-marburg.de       | D-W-3550 Marburg
Bitnet  : HAMPE2 AT DMRHRZ11                           | Germany
Fido    : 2:243/660                                    | Phone +49-6421-28-7092
Fax     : +49-6421-28-4858                             |
Newsgroups: comp.os.ms-windows.programmer.win32
From: daavid@bohra.cpg.oz.au (Daavid Turnbull)
Subject: Install hangs requiring a power down boot!
Organization: Computer Power Software Group Pty Ltd
Date: Wed, 16 Dec 1992 07:33:25 GMT


After waiting many many weeks for the October drop of NT I installed it
almost immediately.

The start of the install occured from a cd mounted in a novell server.

The installation was express, the only anomalie being a couple of tries
at getting the domain info correct for lan manager.

I was very impressed at the quality of the install process up untill it
indicated that it was deleting some interim files, I presume near the end.

At this point the box hung, a cold boot being required to bring it back to
life, no further messages and only a small flurry of disk activity later.

I intend to reinstall again when I have a moment. Does anyone have experience
of this sort of problem?  Was the installation nearly complete? (Everything
that I have tried seems to work ok.)  All clues as to the cause would be
appreciated.
--
	Daavid Turnbull
	daavid@bohra.cpg.oz   +61 3 823 0222    (fax) +61 3 824 8068
	uunet!munnari!bohra.cpg.oz!daavid
	CP Software Export Pty Ltd                   ACN 006 640 133
	(A Division of the Computer Power Group)
	19 Cato Street, Hawthorn, Victoria, Australia, 3123.
Newsgroups: comp.os.ms-windows.programmer.win32
From: RUESS_M@rzmain.rz.uni-ulm.de (Ruess Michael)
Subject: Re: NT server under OS/2 Domain?
Organization: University of Ulm, Germany
Date: Wed, 16 Dec 1992 12:48:50 GMT
X-News-Reader: VMS NEWS 1.24

In <1992Dec15.203247.12023@watson.ibm.com> anzick@watson.ibm.com writes:

> I have tried numerous times to get NT to connect to an OS/2 1.3 Domain controller.
> I go into the Control Panel and into the Advanced of the Network configuration and
> specify the Domain name and it always tells me that either the user name is missing
> or the password is incorrect.
> 
You have to use the Workgroup Name as the Domain name. I have connected my
NT machine with my OS/2 2.0 Lan Server, I think it works the same with the
1.3 Domain controller.


> Since I am an administrator on the OS/2 domain, I tried different things including
> defining the computer name to the domain as a server and adding the NT logged on userid
> as a domain user.
>

Create an account for the NT machine as an additional server on the domain.
Create an account for the username and pass as you are logged on the NT.
On the OS/2 LAN Server, you  have to start the server and then try to view
the NT resources with: NET VIEW \\NT (<-- the name of your NT machine) on
the LAN Server, and try to NET VIEW \\SERVER (<-- name of your OS/2
Server).

Since I cannot run the NETLOGON service on the NT machine, I am not able to
logon on the NT machine but I can use the NT resources with NET USE
command. This is the same for the NT machine.

Hope this helps,

Michael Ruess
University of Ulm, Germany
From: nevries@accucx.cc.ruu.nl (Nico E de Vries)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: Has anyone in Europe got Win NT Oct?
Keywords: Windows NT
Date: 14 Dec 92 18:17:54 GMT
Organization: Academic Computer Centre Utrecht

In <tomwii.724317807@meryl> tomwii@meryl.csd.uu.se (Tomas Wiiand) writes:

>Has anyone outside US got their October release of Win NT?

>I live in Sweden and I still haven't got my October (December?) release!

>/Tomas

I do have access to a legal version of Windows NT October. But how is that 
going to help you? (Posted from the Netherlands)

Nico E. de Vries  (nevries@cc.ruu.nl) |------------------*   AA   III  PPP
_ This text is supplied AS IS, no warranties of any kind |  A  A   I   P  P
| apply. No rights can be derived from this text. This   |  AAAA   I   PPP
| text is likely to contain spelling and grammar errors. |  A  A   I   P
*---------------------------( Donate to GreenPeace! )----*  A  A  III  P

To get (many) ==> LOSSLESS DATA COMPRESSION SOURCES <== get lds_10.zip at 
garbo.uwasa.fi /pc/programming. Make files for Borland C are included.
From: eliel@fringe.cis.brown.edu (Eliel Mamousette)
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Mach32 & 16Meg
Date: 17 Dec 1992 04:26:26 GMT
Organization: Brown University
Distribution: world
Reply-To: Eliel_Mamousette@Brown.EDU
NNTP-Posting-Host: fringe.cis.brown.edu
Keywords: ATI ISA Memory Aperture

Hello,

I was wondering if anyone had found a way to disable or relocate a  
(single?) meg of memory so that the ATI Ultra Pro (on a Vesa bus) 4Meg  
aperture could be enabled?

The documentation says that it is currently impossible to enable the 4meg  
aperture on ISA bus machines with 16Meg of ram, but provides (nor  
suggests) alternative workarounds.

I know the ATI folks are working on developing newer drivrers, which is  
why I thought I'd ask here if anyone had developed a home-grown  
workaround.

By the way, the machine(s) in question is a Gateway2000 486DX2-50 with
16Meg of ram and an ATI Graphics Ultra Pro on the vesa bus....  Gateway,  
being the kind of company that they are, decided to ship the machine to me  
with the latest and greatest of memory architectures, hence I have a  
_single_ 16Meg simm on the mother board, otherwise I would have availed  
myself of the more obvious solution....

thanks in advance,
	eliel
From: msieber@csghsg5a.bitnet
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Documentation on REGEDIT
Date: 14 Dec 92 15:14:31 GMT
Organization: University of St.Gallen, Switzerland

Documentation on REGEDIT needed.

Is there an explanation of REGEDIT.EXE?

Where can I cat informations about the entries in the 
registry-database?

Is there a book about this database?

Maybe a file on accessible via anon ftp?

	Thanks

		Martin Sieber


Newsgroups: comp.os.ms-windows.programmer.win32
From: martin@iastate.edu (Martin R Calsyn)
Subject: Undocumented API calls
Organization: Iowa State University, Ames, IA
Date: Fri, 18 Dec 1992 17:21:24 GMT

I recently posted here and on Compu$erve requesting advice on how to
determine the home directory for a user.  MicroSoft responded on CI$ and
indicated that I should user the HOMEPATH environment variable.  This is
perhaps tolerable for determining the homedir for the currently active
user but not real desirable since it's a secondary, non-secure source of
that information.

It's not really workable in the larger sense because you can't get at
the homedir and other profile info for an arbitrary user that way (as
might be needed by certain user-administration programs).  In any case,
MS has been responsive and is examining the issue and as I understand
it, considering whether to `expose' the calls they use.

In a related issue (which I posed on CI$ this AM), there are plenty of
routines for managing security objects, but the one conspicuous by its
absence is the routine to take a user name and password and get back an
access token.  Unless I've developed a documentation blind-spot, then
it's just not there.

I'm in the process of porting ftpd, which will turn out to be an
impossible task if I can't use the supplied name and password to obtain
tokens, etc with which to control file access.  The same would be true
of any attempt to port telnetd or any other application which does not
get its token from WINLOGON, the services manager, or by using a
client-provided token (impersonation).

Have I missed something technical here or is MS keeping some pieces of
the puzzle to themselves?

-- 
Martin R. Calsyn                                   martin@iastate.edu
Software Innovations Incorporated                  voice: (515) 232-9196
P.O. Box 644                                              (800) 728-1525
Ames, Iowa 50010                                   fax:   (515) 233-6209
From: ken@minster.york.ac.uk
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Re: TCP/IP access into NT
Date: 14 Dec 92 15:18:24 GMT
Organization: Department of Computer Science, University of York, England

Greg Kochaniak (greg@ansoft.com) wrote:
: In article <723981859.12122@minster.york.ac.uk> ken@minster.york.ac.uk writes:
: >James 'J' Allard (jallard@microsoft.com) wrote:
: >
: >I have a more thorny problem: I thought the winsock API was visible to 16bit
: >windows apps? I have an X windows client (vista eXceed) which will talk to
: >about 15 different transports, one of which is the winsock protocol. But I
: >can't get it to work (I've tried "TCP" in the services control panel) -
: >whenever I run eXceed I just get a message box moaning about "no transport".
: 
: I don't think Vista eXceed/W is compatible with the winsock protocol yet.
: I have here ver. 3.0.1 and an offer to upgrade to 3.2. The offer specifies
: 15 different TCP/IP transport implemented by different companies, but does
: not mention Winsock at all. But I would love to discover that I'm mistaken
: about that and that eXceed/W can run under NT. Were you or anybody else
: able to run other Winsock 16 bit application under NT?

Well, I asked it  to use MS DOS TCPIP, and it tried to bind to WINSOCK.DLL
(eXceed installed this in the \EXCEEDW\MS directory). It binds to it, but
then says "network not up" or something close.

--
Ken Tindell             Internet      : ken@minster.york.ac.uk
Computer Science Dept., Local FTP site: minster.york.ac.uk
York University,        Tel.          : +44-904-433244         
YO1 5DD, UK             Fax.          : +44-904-432708
--
"The Gulf War won't be like a Rambo film; it will be long, bloody and terrible"
Newsgroups: comp.os.ms-windows.programmer.win32
From: margaret%asylum.cs.utah.edu@cs.utah.edu (Malgorzata Sturgill)
Subject: Re: Windows for Workgroups & Windows NT
Date: 17 Dec 92 08:50:30 MST
Organization: University of Utah CS Dept

In article <wright.85.0@lims01.lerc.nasa.gov> wright@lims01.lerc.nasa.gov (Ted Wright) writes:
>Can I access a shared NT drive from Windows for Workgroups?
>Can I access a shared Windows for Workgroups drive from Windows NT?
>
>Thanks, 
>
>Ted Wright (wright@lims01.lerc.nasa.gov)

We have two PC at home on an ethernet, one running Windows for
Workgroups, and one with NT. We are able to share discs on both systems
without any problem. The only inconvinience was that drives have to be
speciffied manually, instead of being chosen from the menu of sharable
drives. By the way I am able to acess the CD rom on the NT system from
the WfW machine.  also if you use MS-DOS prompt on the WfW systems then
the shared drives will be visible there.

If you are using Windows for Workgroups for printing and the printer is
on the NT side, make sure that you do not attempt to choose the printer
from the menu of available shared printers - this will cause a lan rror
that on my WfW system required a reboot to fix. Instead just type the
network name of the printer.


				Hope this helps.
					m.



Malgorzata Marek Sturgill		margaret@cs.utah.edu

"At ACME Looniversity we earn our toon degree"
		-- Tiny Toons
Newsgroups: comp.os.ms-windows.programmer.win32
From: cnolan@vax1.tcd.ie
Subject: Error codes please!
Organization: Trinity College Dublin
Date: Mon, 14 Dec 1992 15:20:24 GMT

Can someone in Microsoft please please please post a list of error codes?
Especially startup errors.

Also will their be an Oct release FAQ?

--
===============================================================================
		Conor Nolan	(cnolan@tcd.ie)
	Microelectronics Dept. Trinity College, Dublin.  IRELAND.
===============================================================================
From: msieber@csghsg5a.bitnet
Newsgroups: comp.os.ms-windows.programmer.win32
Subject: Error 6003 Division / 0 at DOS-Progs..
Date: 14 Dec 92 14:50:23 GMT
Organization: University of St.Gallen, Switzerland

DOS and Windows 16-bit Programs don't run.

When starting a DOS program, a Text-Window is being created, 
then there's the 'Division through 0' (or similar) error.

This happens with all DOS-Program (for example QEDIT), not only
with games that "directly access the hardware".

I got a 486 33 with 16MB Ram and AMI-BIOS.

When starting a 16-Bit Windows-Program, there's an hourglass
for half a second (a bit longer at the first Windows program),
and then there happens nothing.

I disabled the external and internal cache and switched from
Turbo to normal mode (8 MHz). Then after starting a DOS-Program
there appeared the message

	16-Bit DOS - Application

	NTVDM.DLL has encountered a system-error
	with QEDIT

Since this message appears only for fractions of a second, I couldnt
exactly read it.

Windows Programs didn't run either.

How can I fix this bug?

Thanks for all suggestions.

	Martin Sieber
 
Newsgroups: comp.os.ms-windows.programmer.win32
From: kewta@solomon.technet.sg (Kew Tow Ann)
Subject: Installation Problem on EISA KT486/33
Organization: TECHNET, Singapore
X-Newsreader: TIN [version 1.1 PL8]
Date: Wed, 16 Dec 1992 10:48:36 GMT


 Help desperately needed!
My system configuration is a EISA based KT486/33 with 16 MB RAM, 647 MB
harddisk and a Hitachi CDR1700S CD ROM. I chose to use the dos2nt option for
setting up as the CDROM is not supported. My Windows NT is the July 92
version.

The installation was smooth. I set up my CD ROM following the installation
procedure and could get it up and recognised as drive d: Next I followed the
installation guide in Windows NT using the dos2nt option and could get up to
Step 7 pg 11 of the release notes.
When I reboot the system, I get the following message:

 WARNING! - Incorrect EISA memory configuration information
            Windows NT will use the ISA memory configuration information.

Anybody has any idea what this mean?

The system then goes into the Flexboot and when I selected Windows NT, it
gave the following message and hang:

  Microsft Windows NT  - Preliminary release for Developers
  MmInit : 16064 Kb Available Memory
  Fatal System Error : 0x00000069
  Phase 1 I/O initialization failed

After this, the system completely hangs and only RESET could get it back.
Ctrl-Alt-Del doesn't worked. I tried reinstalling  it a couple more times
with the same results. I hope someone out there can help me.

Thanks and regards.


Newsgroups: comp.os.ms-windows.programmer.win32