************************************************************************ Windows NT FAQ List for Forum MSWIN32 (August 1, 92) ************************************************************************ Trap 0x0000000E Question: When using the preferred graphical install method I get a Trap 0xE. What is wrong? Answer: This is a known problem which has several work-arounds available depending on the hardware configuration. The most common problem is due to a bug in the 3.5 inch BOOT DISK. If you are using this disk to install the kit and observe this problem, simply make a disk copy of the working 5.25 inch disk. You must make an exact duplicate of this disk onto a new 3.5 inch 1.44MB floppy disk. Assuming you have the 3.5 inch disk as your A: drive and the 5.25 inch disk as your B: drive, follow these steps: * Boot into your systems CMOS program. * Change the setting for the 3.5 inch disk to a 1.2 MB 5.25 inch disk. * Boot MS-DOS. * Make a copy of the 1.2 MB disk by inserting a blank disk in A: and the 5.25 BOOT DISK in B: drive. Run 'DISKCOPY B: A:'. * Boot back into your systems CMOS program. * Change the setting for the 3.5 inch disk back to a 1.44 MB disk. * Insert the new 3.5 inch 1.2 MB format BOOT DISK into A: and reboot. Note: you may need to remove any existing \winnt directory found on your hard disk first before running the install. Another common work around is to disable one or more of the following: * All BIOS shadowing. * All video shadowing. * All external CPU caches. * The Turbo switch (i.e. run the system at the slowest speed). ************************************************************************ CVPACK: Fatal error CK1007: invalid Types table in module In this release of Windows NT, there is a problem with the cvpack utility; which results in the error "CVPACK: Fatal error CK1007: invalid Types table in module". CVPACK is compressing debug information in the executable. This step is required for source level debugging. As a work around to this problem, to create an executable, compile without the /Zi switch. This will result in no debug information in the object modules. Alternatively, you can remove the debug options during linking. The samples default to -debug:full and -debugtype:full. Do not link with either of these options. This should allow you to create an executable for testing purposes while we investigate the cvpack problem. ************************************************************************ Sample Requests: If you have a sample request for the next release (or possibly to be released on CompuServe) please write out the details of your request and send them to >internet:sdksamp@microsoft.com. Also please include any information about your need that might be relavent to tailor the sample to your need. Please note that this is a one way alias, and that we are not likely to respond by confirming the receipt of the request. And also note that we may not have the resources to create all the samples requested. But we will do our best based on need and resources. ************************************************************************ Device Driver Requests: Our standard means of releasing drivers is with our CD releases. Although we are not committing ourselves to continue this practice, currently all fixed, updated, or new device drivers are being posted on Forum: WinNT, Lib 2. We are currently making every attempt to keep this library updated with drivers as they become available. If you have hardware that is not currently supported , or does not have a driver posted in WinNT, Lib 2; please make a device driver request by filling out the hwfeed.txt form and mail it to us at >internet:winnthw@microsoft.com. Please be aware that because of our support demands right now, this is a one way alias; we are not likely to respond directly to you to confirm that we have received your request. The hardware compatibility list can be found in MSWIN32, Lib 17. 0692hw.txt. Hwfeed.txt can be found in MSWIN32, Lib 17; or WINNT, Lib 1. In order to send mail to the address mentioned via CompuServe, you have to: * Leave the forum. * At any "!" prompt, enter GO MAIL. * Mail your request to: ">internet:winnthw@microsoft.com" ************************************************************************ Unicode Level of Support: The July Preliminary Release of Windows NT SDK is a full unicode implementation. It supports unicode applications. However, an alternate input editors is not yet available. Glyphs will be suitable for the Roman languages. Glyphs for Kanji are not yet available. ************************************************************************ DELL Machine Only Recognize 16 MB of Memory Summary: The ISA Dell 486D/50 25/50Mhz has a bios problem which prevents it from seeing greater than 16MB of RAM under NT. More Information: The ISA Dell 486D/50 25/50Mhz machine does not see greater than 16Mb of RAM under Windows NT. This is a known problem with the bios of the Dell machine. Dell is producing a upgrade to the bios which should be available August 92. If your machine demonstrates this problem, please contact Dell after July 92 to receive their A08 bios upgrade. ************************************************************************ Missing C++ Header Files: (iostream.h) Summary: The iostream.h file was not included on the NT pre-release CD. It is necessary in order for an application to make use of C++ I/O. More Information: This file will be posted to Compuserve as soon as it is ready and tested. Until then, the suggested work around is to use printf() and stdio.h. ************************************************************************ Requests for DDK or DDK Support At present a Windows NT DDK is not available. Several people at Microsoft are currently working very hard to get the Windows NT DDK ready for distribution. If you would like to be placed on the mailing list for information about this kit please send mail to: winntddk@microsoft.com (prepend '>INTERNET:' to this string if you are mailing from Compuserve). Please be aware that this is a one way alias, and that there will be no email response/confirmation to your request. Thank you for your interest. ************************************************************************ TCP/IP Support: TCP/IP including ftp and some other tcp utilities is included in the July preliminary Win32 development kit for NT Source routing are not included in the July version of TCP/IP, which implies TCP/IP isn't supported on token ring cards for this release, and LM2.1 clients aren't able to access NT servers across TCP/IP, regardless of the net card in the NT server. Source routing will be in later version of NT TCP/IP. Source routing is in the July version of NETBEUI, so some token ring cards are supported (see 0692HW.TXT in lib 17), and LM2.1 clients can access NT servers running the July version of NETBEUI ************************************************************************ Windows NT is a Preliminary Release, not a Beta: Windows NT is not yet in Beta. The Win32 SDK for Windows NT is a "Preliminary" release, intended for development of 32-bit applications for Windows. Our focus has been on the Windows NT Kernel and Win32 API. The SDK does not include POSIX support and we have not yet had an opportunity to complete testing of our support of 16-bit Windows and MS-DOS applications. Therefore, the SDK is not appropriate for Beta test and evaluation. There will be a very broad Beta program in the early fall that is intended for end-users. This release will include full support for MS-DOS, 16-bit Windows and POSIX applications. For our non-developer customers who wish to obtain a beta release of Windows NT, please stay tuned to the forum for availability and further details. ************************************************************************ Hareware Compatibility List: There is a hardware compatibility list which came with your release of Windows NT. It has also been posted on CompuServe, forum MSWin32, Lib 17, filename: 0692HW.TXT. Hardware listed in this file has been preliminarily tested on the July 92 release of Windows NT, and is supported. We do not claim that hardware not on this list will not run; however, it has not been tested and it is not supported at this time. ************************************************************************ MSDN: Microsoft Developers Network CD: The MSDN offers a quarterly paper and a CD program. The CD is intended to help developers with writing Microsoft Windows applications. The first pre-release beta CD contains 34,000 pages containing: complete copies of Microsoft Journals (MSJs); samples and source code; MS Press books; tools; and articles covering programming, technical, and strategic information for Windows. This first planned shipping date of pre-release MSDN CD will be in September. Those developers who attended the PDC are already enrolled in the pre-release program, and are on the regular mailing list. They will receive the first two pre-release CDs free of charge. Those developers who receive the Developer Network News should receive a pre-release program offer. For those developers who did not attend the PDC and do not receive the Developer Network News (and the pre-release program offer in the mail) can call the Developer Service Team at 800-227-4679 x11771 to get enrolled in the pre-release program for $30. ************************************************************************ Bernoulli and Removeable Media Not Supported: Bernoulli boxes and removable SCSI drives were not tested with this release of Windows NT, and do not appear on the hardware compatibility list. Since the release we have seen evidence that Windows NT has some problems with these devices. We are aggresively pursuing this matter in hopes of having it resolved by the next release. ************************************************************************ Adaptec AHA 1542B Driver Can Cause Fatal System Error: Summary: There is a known problem with the Adaptec AHA-1542B driver which causes fatal system errors under some circumstances. More Info: The problem is triggered by simultaneous I/O with the floppy and the hard disk. This will be corrected in the next release. To avoid this you may want to use an alternative floppy controller and disable he one on the Adaptec. ************************************************************************ The System Uses About 70 Threads: With this release of Windows NT, Pview will show that the system running without any active applications will use about 70 threads. This is normal for this release. The majority of theses threads are system threads. ************************************************************************