CONTACTS 

SUBJECTS
Disk Investigator 1.1 Freeware by Kevin Solway Installed on C13
C13 Install Disk Investigator v 1.1
FAT32 Format Option Not Shown by W2K During Installation
C11 Install Disk Investigator v 1.1
Disk Investigator Microsoft Utility Shows Contents of Disk
Clean Install Windows 2000 Formatted FAT16 Instead of FAT32
SRX020519601225 Microsoft Incident Number to Investigate How to Conve
2 Incidents for Retail Purchasers
2 Incidents Free Support for Installing Retail Version of W2K
1 Free Incident Used Support for FAT32 Format Problem
FAT32 Failed on Installation Only Option was FAT16 or NTFS

1313 -    ..
1314 - Summary/Objective
1315 -
131501 - Follow up ref SDS 9 0000, ref SDS 8 0000.
131502 -
131503 -
131504 -
131505 -
131506 -
131507 -
1316 -
1317 -
1318 - Progress
1319 -
131901 - On 020416 we encountered a problem installing w2k on c11 in Concord
131902 - because disk format was reported as FAT rather than FAT32.
131903 -
131904 - As a result, there is an action item to investigate whether this is an
131905 - error in reporting by w2k, or if there was an error by w2k in not
131906 - providing a FAT32 format. ref SDS 8 1S9L
131907 - ..
131908 - Today, I am in Concord and so installed Disk Investigator
131909 - received on 020502. ref SDS 9 0001
131910 -
131911 - It shows the I drive on c11 is FAT16, which seems to conflict with
131912 - understanding from Brent on 020502 that w2k cannot format FAT16, and
131913 - can only format FAT32 or NTFS. ref SDS 9 BM9N
131914 -
131915 - Disk Investigator shows....
131916 -
131917 -
131918 -                       c: Drive         i: drive
131919 -
131920 -    Cluster size         4096             32768
131921 -
131922 -    File system          FAT32            FAT16
131923 - ..
131924 - This condition shows a lot of space is lost.
131925 -
131926 -
131927 -
131928 -
131929 -  ..
1320 -
1321 -
1322 - 1333
1323 -
132301 - Called Microsoft to follow up on support on 020416 for installing w2k
132302 - clean. ref SDS 8 I69K
132303 -
132304 - Talked to Shawn.  Explained problem.
132305 -
132306 - Shawn asked for project registration number which is in system
132307 - properties opened by right click on system management....
132308 -
132309 -
132310 -                      51873-006-5958492-09635
132311 -
132312 - ..
132313 - Shawn advised that we have two incidents of commercial support
132314 - still open.
132315 - ..
132316 - He is using one of them now.
132317 -
132318 -
132319 -                      SRX020519601225
132320 -
132321 -
132322 - So, we have one incident left.
132323 -
132324 - This is a big improvement on Microsoft charging $245 to fix problems
132325 - with w2k reported on 010207. ref SDS 4 B46N
132326 -
132327 - Shawn transferred the call to a technical engineer.
132328 -
132329 -
132330 -
132331 -  ..
1324 -
1325 -
1326 - 1352
1327 -
132701 - Talked to Nathan Edwards.   425 635 2997 ext 33538
132702 -
132703 -       v-2nated@mssupport.microsoft.com
132704 -
132705 - He says that if w2k is installed on a drive partition that is less
132706 - than 2G, then it only offers option to format for FAT16 or NTFS.
132707 -
132708 -     Nathan's second letter confirms this understanding, ref DRT 2
132709 -     SQ7O, received below. ref SDS 0 7O4H
132710 - ..
132711 - Nathan said Microsoft has not figured out how to let customer's
132712 - who buy w2k to configure FAT32 on partitions that are less than 2 GB
132713 - during a clean install.
132714 - ..
132715 - This computer had a FAT32 i drive when purchased new, because it
132716 - had w98, which supported this capability.  W2K was installed as an
132717 - update on 000310 and at that time it retained the original format.
132718 - There is no information in the record saying W2K only permits
132719 - formatting a drive for FAT32 that is over 2 GB.
132720 -
132721 - Nathan asked about formatting for NTFS.  He explained that w2k
132722 - supports converting a drive to NTFS, but not to FAT32.
132723 -
132724 - We reviewed the record on 010205 showing information that people have
132725 - had a variety of problems with NTFS. ref SDS 3 EH8I
132726 -
132727 -  ..
132728 - Nathan there is a program...
132729 -
132730 -
132731 -                       Partition Magic
132732 -
132733 -
132734 - ...may be able to convert a FAT16 partition to FAT32 running under
132735 - w2k.
132736 -
132737 - We reviewed again whether w2k has improved management of NTFS
132738 - partitions?
132739 -
132740 - Nathon related experience having used NTFS drives for several years
132741 - without incident.  He said files can be copied between NTFS and FAT32
132742 - partititions.  NTFS supports security features that are not available
132743 - in FAT32, and so if an NTFS file is copied to a FAT32 partition, then
132744 - the security flags are not supported on the FAT32 partition.
132745 - ..
132746 - Decided to convert to NTFS.
132747 -
132748 - Nathan explained to....
132749 -
132750 -    Use following command at DOS prompt:
132751 -
132752 -
132753 -              convert i: /fs:ntfs
132754 -
132755 -
132756 -    DOS prompt can be opened by entering....
132757 -
132758 -
132759 -                     cmd
132760 -
132761 -
132762 -    ...in the Start Run option.
132763 - ..
132764 - We ran this and it recovered about 200 MB of disk space.
132765 -
132766 - Thanked Nathan for his help, and congratulated Microsoft on
132767 - significant improvements in supporting customers.
132768 -
132769 -
132770 -
132771 -  ..
1328 -
1329 -
1330 - 1558
1331 -
133101 - Received ref DRT 1 0001 from Nathan confirming assignment of the
133102 - problem incident, and explaining TQM stuff about contacting Nathan's
133103 - boss to help expedite performance. ref DRT 1 S144
133104 -
133105 - Nathan correctly explains the scope of work. ref DRT 1 KR7N
133106 -
133107 -    Contact information is provided. ref DRT 1 006N
133108 -
133109 -
133110 -
133111 -  ..
1332 -
1333 -
1334 - 2203
1335 -
133501 - Received ref DRT 2 0001 from Nathan confirming progress solving this
133502 - problem, and noting the case can be archived. ref DRT 2 MP8H
133503 -
133504 -    Nathan says to let him know if there is any follow up.
133505 -
133506 -
133507 -
133508 -
133509 -
133510 -
1336 -

SUBJECTS
SRX020519601479 Microsoft Called and Got Incident Number to Investiga
DOS Memory Get 750K Instead of 634K
DOS Technical Support
DOS Memory Program for More than 640K
Memory Above 640K Submit SDS Program for Review by Brandon
DOS Memory Above 640K
640K Memory Limit for DOS Need Solution
640K RAM Increase to 700K+

2011 -
201101 -  ..
201102 - Increase Memory for SDS Above 640K
201103 -
201104 -
201105 - Asked about using memory above 640K?
201106 -
201107 - Nathan said that is another incident number.  So, we used the 2nd of
201108 - our two incidents.
201109 - ..
201110 - Talked to Thang.
201111 -
201112 -
201113 -                       SRX020519601479
201114 -
201115 - ..
201116 - Talked to Ian Blew     425 635 2997 ext 32515
201117 -
201118 -
201119 -           v-1iabl@mssupport.microsoft.com
201120 -
201121 - ..
201122 - Explained objective to use memory above 640K, by, for example,
201123 - turning off CGA memory, so that DOS "mem" command shows the "largest
201124 - executable program size is 740K, as reported in the record on 930720
201125 - that reviews solution available in OS2. ref SDS 1 5955
201126 -
201127 - Currently we have 634K running NTVDM in W2K; increasing this to above
201128 - 740K achieved by OS2 would significantly strengthen ability of
201129 - Microsoft to improve enterprise management for saving time and money,
201130 - as explained in POIMS. ref OF 1 6221  On 010510 Steve Balmer stated
201131 - Microsoft policy to improve customer productivity. ref SDS 7 YG5K
201132 -
201133 - On 930814 Morris considered ideas for accomplishing this objective
201134 - that required input from Microsoft, which was difficult to obtain at
201135 - that time. ref SDS 2 OX3L  Perhaps Microsoft can contribute at this
201136 - time.
201137 -
201138 -       [On 020613 Morris submitted questions to Microsoft to clarify
201139 -       ideas on a solution. ref SDS 14 QU4O
201140 - ..
201141 - Ian could not find a solution in the Microsoft Knowledge Base.
201142 -
201143 - He put our call on hold to investigate by makeing a few calls.
201144 -
201145 -
201146 -  ..
2012 -
2013 -
2014 - 1540
2015 -
201501 - Ian came back on line.  He has found someone who can contribute to a
201502 - solution.
201503 -
201504 - Transferred to Brandon Robinson; Ian remained on the line.
201505 - ..
201506 - We reviewed the objective of improving memory management for
201507 - SDS, per above. ref SDS 0 LQ4M  SDS is written in 8088 assembly
201508 - language and has an upper limit of addressing 1 MB of RAM.  We want
201509 - to modify the program to use memory above 640K to the 1 MB limit.
201510 - ..
201511 - Brandon explained that IBM accomplished 740K for largest
201512 - executable program size by using memory that is no longer available
201513 - because Microsoft Windows 2000 works differently.
201514 - ..
201515 - Brandon seemed to indicate that Microsoft no longer allocates
201516 - memory above 640K, so there are no unused blocks available as IBM was
201517 - able to make available to customers using OS2.
201518 -
201519 -     This proposition seems somewhat incorrect, since many programs use
201520 -     various hardware device drivers that are wired to address I/O
201521 -     resources based on the prior design of DOS between 640K to 1M.
201522 -
201523 -     If someone at Microsoft has changed the operating system so the
201524 -     computer cannot not use the memory address between 640K - 1M for
201525 -     DOS, then someone can change it back.  This is a human problem,
201526 -     not one of resources.
201527 -
201528 - Brandon asked about sending the SDS program to him via email so he
201529 - can investigate ways for solving the problem.
201530 -     ..
201531 -     On 930814 Morris considered ideas for improving productivity
201532 -     of SDS by increasing memory which seemed to require support from
201533 -     Microsoft. ref SDS 2 6333  Perhaps Brandon's review could address
201534 -     Morris' ideas.
201535 -     ..
201536 -     Brandon's letter received later this afternoon confirms the
201537 -     scope of the problem, but does not say anything about sending him
201538 -     the SDS code, per below. ref SDS 0 I27O
201539 -
201540 -          [On 020522 Brandon reviewing e.exe. ref SDS 11 0001
201541 -
201542 -          [On 020606 called to follow up, talked to Brandon's
201543 -          colleague, Brenda Cannon. ref SDS 12 RZ5N
201544 -
201545 -          [On 020611 Brandon recommends re-writing the progrma in a
201546 -          current operating system; requested support for interim
201547 -          solution, per scope of current problem. ref SDS 13 BL8K
201548 -
201549 -
201550 -
201551 -
201552 -
201553 -
201554 -
201555 -
201556 -
201557 -
201558 -
2016 -

SUBJECTS
Memory Above 640K Vmware and Similar Programs May Solve Problem
Vmware and Similar Programs Medit Microsoft Suggests Might Solve 640K
Vmware and Similr Programs Use to Solve 640K Memory Problem
Vmware Evaluation Failed

2407 -
240701 -  ..
240702 - Vmare and Similar Capabilities Suggested to Solve 640K Memory Problem
240703 -
240704 - There was discussion that some Microsoft people use the following
240705 - programs to increase memory available for DOS applications above
240706 - 640K....
240707 -
240708 -                 Vmware
240709 -                 Virtual PC
240710 -                 Bochs
240711 - ..
240712 - Microsoft does not recommend these products.
240713 -
240714 -     The general procedure is to install the programs, then install
240715 -     DOS 6.22, and configure it to run our DOS app.
240716 -
240717 -     Brandon seemed to indicate we cannot run DOS 7 because it is
240718 -     for Windows 98 and W2K both running NTVD.
240719 -
240720 -    [On 020522 Brandon reports largest executable program size using
240721 -    Vmware is 617K. ref SDS 11 RN6I
240722 -
240723 - Brandon is taking control of this case number and will keep it open
240724 - for a week.
240725 - ..
240726 - He will send an email to confirm these discussions.
240727 -
240728 - Brandon asked if he can look at the code for SDS to see if there might
240729 - be a way to increase memory without the intermediary program.
240730 -
240731 -
240732 -  ..
2408 -
2409 -
2410 - 1912
2411 -
241101 - Received ref DRT 3 0001 from Brandon confirming scope of this problem.
241102 -
241103 - Brandon says in part...
241104 -
241105 -     As we discussed, the issue you're experiencing is memory usage
241106 -     questions in the NT/2000 enviroment.  Once we resolve this issue,
241107 -     verification will be provided through email. This will allow us to
241108 -     make absolutely sure we have completed the agreed upon incident.
241109 -     ref DRT 3 2V7G
241110 -     ..
241111 -     We shall be working to resolve this specific issue through
241112 -     the course of the case. If I have misunderstood your concern
241113 -     please let me know.  According to our last contact, I will contact
241114 -     you again on (date and time) via (e-mail or phone). ref DRT 3 GV7M
241115 - ..
241116 - Brandon's signature block shows support for enterprise
241117 - management, ref DRT 3 KD9G, which aligns with objectives of SDS, as
241118 - shown in POIMS. ref OF 1 6221
241119 -
241120 - Tried Brandon's suggestion....
241121 -
241122 -
241123 -
241124 -  ..
241125 - Vmware Investigated and Trial Downloaded for Evaluation
241126 -
241127 - Found address for Vmware...
241128 -
241129 -
241130 -           http://www.vmware.com/
241131 -
241132 -  ..
241133 -
241134 - ....costs v. 3.1 for download.................... $299
241135 -
241136 - Vmware description....
241137 -
241138 -   http://www.vmware.com/products/desktop/ws_features.html
241139 -
241140 -     VMware Workstation is virtual machine software for technical
241141 -     professionals. It lets you work on multiple operating systems on a
241142 -     single computer. You spend less time configuring hardware,
241143 -     installing software, and rebooting or reconfiguring systems, and
241144 -     more time developing, testing, and deploying applications and
241145 -     delivering support. VMware Workstation gives you immediate access
241146 -     to the operating systems and applications you need to get your job
241147 -     done now.
241148 - ..
241149 - There is discussion of a Virtual Disk under FAQ at....
241150 -
241151 -    http://www.vmware.com/products/desktop/ws_faqs.html
241152 -
241153 - ....which indicates the DOS files would be managed differently from
241154 - the way they exist on the disk under W2K.  Hopefully this is an
241155 - incorrect inference.
241156 -
241157 -      Virtual disks are the disk partitions of virtual machines. They
241158 -      are stored as a file on the file system of your host operating
241159 -      system. Since an entire disk partition is saved as a file, it is
241160 -      easy to backup, move and copy. You can even share virtual disks
241161 -      from a file server.
241162 -
241163 - ..
241164 - Can download an evaluation copy of Vmware for 30 days at...
241165 -
241166 -
241167 -           http://www.vmware.com/download/
241168 -
241169 -     VMware makes our software available for evaluation by prospective
241170 -     customers.
241171 -
241172 -     You may evaluate VMware Workstation for a 30-day period. To
241173 -     evaluate VMware Workstation (for Windows or Linux operating
241174 -     systems), please do the following:
241175 -
241176 -       1.  Click here to register for a license key that is
241177 -           valid for 30 days only.
241178 -           ..
241179 -       2.  For best results, read the VMware Workstation 3.1
241180 -           Evaluation FAQs for installation and troubleshooting tips.
241181 -
241182 -       3.  After your 30-day evaluation license has expired, go to
241183 -           VMware Web Store to purchase your copy of VMware
241184 -           Workstation.
241185 -
241186 -
241187 - Signed up for evaluation.
241188 -
241189 -  ..
241190 - Recieved evaluation serial number.....
241191 -
241192 -
241193 -                     6079D-CKT24-RCQ23-3UM04
241194 -
241195 - ..
241196 - Downloaded program installation file about 18MB at....
241197 -
241198 -        http://www.vmware.com/download/workstation.html
241199 -
241200 -
241201 -         vmware-workstation-3.1.1-1790.exe
241202 -
241203 -
241204 - Ran the program and installed in...
241205 -
241206 -
241207 -                        h: 00 30
241208 -
241209 -
241210 - Booted computer to complete installation.
241211 - ..
241212 - Launching the program opens something for entering a "serial
241213 - number" which evidently is the registration number received in the
241214 - letter from Vmware, per above. ref SDS 0 JQ8H
241215 -
241216 - Next is a registration action.
241217 -
241218 - Since we have a dial up connection here, connected to the ISP.
241219 -
241220 - Clicked "Register Now" option.
241221 -
241222 - Got a screen with a "Register" option, which is the same thing we did
241223 - to get the evaluation program.  Clicked the Register option and this
241224 - opened a screen with the serial number received from Vmware already
241225 - entered, and more boxes to enter name, address, etc., which we
241226 - entered previously.  This effort crashed by reporting our email is
241227 - already assigned, reflecting the earlier activity when these steps
241228 - were performed.
241229 - ..
241230 - Was able to launch a Virtual Machine.
241231 -
241232 - It asks where to put it, so tried....
241233 -
241234 -
241235 -                      c: ds
241236 -
241237 -
241238 - ....for DOS.
241239 -
241240 - The problem is that now it wants installation files on a disk, so it
241241 - can configure the Vmware workstation.
241242 -
241243 - Will try to create a DOS 6.22 disk using the code on...
241244 -
241245 -
241246 -                       c: 00 01
241247 -
241248 - ..
241249 - Do not seem to have sys.com in the DOS 6.22 code on c11 in
241250 - Concord.
241251 -
241252 - Drove to San Francisco, and got it from disks.  Set up c13 so
241253 - everything is on the hard drive.
241254 -
241255 -
241256 -  ..
2413 -
2414 -
2415 - 2246
2416 -
241601 - In San Francisco, will try to set up Vmware on c13.
241602 -
241603 - Found original MS DOS v 6.22 code on disks 1 - 3 and copied to...
241604 -
241605 -
241606 -                        g: 00 DOS622
241607 -
241608 -
241609 - ...so that we have ability to create floppy disks in the future.
241610 -
241611 -
241612 -
241613 -  ..
241614 - Installed Vmware on c13 to Evaluate Program...
241615 -
241616 -
241617 -                      c13 h: 00 30
241618 -
241619 -
241620 - Did not register, because did that for c11 earlier, per above.
241621 -
241622 - After installing vmware, ran the program, and configured an MS DOS
241623 - virtual machine, designating the directory...
241624 -
241625 -
241626 -                          c: 00 01
241627 -
241628 - ..
241629 - For the DOS software.
241630 - ..
241631 - Selected "custom configuration."
241632 -
241633 - There is an option to give the DOS virtual machine direct access to
241634 - files on the disk, and there is the following warning...
241635 -
241636 -       WARNING: Use of this feature is for advanced users only and may
241637 -       cause loss of data or inability to boot, particularly when this
241638 -       raw disk partition is used as the boot device. Only limited
241639 -       support is available for this feature. For the most current
241640 -       documentation, please see our Web site at
241641 -
241642 -            http://www.vmware.com/support/ws3/doc/disks_ws.html
241643 -
241644 -       ....and click the link "Installing an Operating System onto a
241645 -       Raw Partition from a Virtual Machine".
241646 - ..
241647 - Did this because we want to create and use files interchangeably
241648 - between the standard configuration under w2k, and anything else.
241649 - ..
241650 - We get a list of partitions for allowing access by the Vmware
241651 - DOS application, and it says....
241652 -
241653 -
241654 -     partition 0            MBR                 31.50 KB
241655 -     partition 1  c         Win95FAT32           6.50 GB
241656 -     partition 2            Win95 Ext'd (LBA)   36.88 GB
241657 -     partition 3  d         Win95FAT32           3.91 GB
241658 -     partition 4  e         Win95FAT32           3.91 GB
241659 -     partition 5  f         Win95FAT32           3.91 GB
241660 -     partition 6  g         Win95FAT32           8.79 GB
241661 -     partition 7  h         Win95FAT32           8.79 GB
241662 -     partition 8  i         Win95FAT32           7.59 GB
241663 -
241664 - ..
241665 - Not sure about partition 0 and 2 so set them to "hide" status,
241666 - and also set partition 8 to "hide," which seems to correspond to
241667 - partition i where the operating system is located.
241668 -
241669 -
241670 -
241671 -  ..
241672 - Vmware Failed to Allocate More than 600K to Executable Program
241673 -
241674 - Spent several hours trying various options and avenues for using
241675 - Vmware that resulted in a record showing this method does not increase
241676 - memory for SDS above about 600K, which is less than w2k allocates.
241677 -
241678 -      [On 020521 notified Brandon of results so far. ref SDS 10 JG9L
241679 -
241680 -     1.  We attempted to tell vmware to use, read and write for...
241681 -
241682 -                     c, d, e, f, g, h and i
241683 -
241684 -         Intially, we set i: to "hide" per above, but in trying to get
241685 -         DOS configured, various error messages led to including i for
241686 -         the purpose of trying the thing.
241687 -         ..
241688 -     2.  Power on, launches the vmware DOS operation.
241689 -
241690 -         This thing will only look at the a: drive.  There is not an
241691 -         evident method to tell the configuration to look at g: where
241692 -         we put the software.
241693 -
241694 -         So, we tried putting a DOS 6.22 disk in the a: drive, and
241695 -         vmware read it.
241696 -
241697 -         With the original MS DOS disk 1, vmware ran setup.
241698 -
241699 -         Running the vmware operation in a window, the keyboard would
241700 -         not work.
241701 -
241702 -         Figured out that we could jump to full screen mode and use the
241703 -         keybaord.  This is totally unacceptable, since we always run
241704 -         SDS in a window, so we have many sessions open, plus do other
241705 -         things when necessary.
241706 -         ..
241707 -     3.  Power on was then tried with a boot disk for DOS 6.22.
241708 -
241709 -         This ran and produced an a: prompt, but could not change to
241710 -         c:, d: or anything else, even though during configuration, we
241711 -         identified all of the partitions for read and write, per
241712 -         above. ref SDS 0 JF6V
241713 -
241714 -         We lose control of the mouse in windows mode, when vmware is
241715 -         running, so cannot switch between applications.
241716 -         ..
241717 -     4.  Ran mem command.  It shows roughtly for the virtual
241718 -         machine...
241719 -
241720 -               total memory...................... 16 MB
241721 -
241722 -               Total conventional memory........ 640 K
241723 -
241724 -               Total executable program size.....580 K
241725 -
241726 -         This is far below what is available in w2k using the NTVD, so
241727 -         it is not clear what benefit vmware offers for SDS relative
241728 -         to running in w2k.  This is not the same as OS2 provides
241729 -         where total executable program size is about 750KB.
241730 -         ..
241731 -         If total executable program size was 800K, or 750K, or
241732 -         even 700K that would be an appreciable benefit.
241733 -
241734 - ..
241735 - Virtual PC investigation at....
241736 -
241737 -
241738 -           http://preview.connectix.com/trial/
241739 -
241740 -
241741 - Research at this location gives an explanation that is similar to
241742 - vmware, per above. ref SDS 0 I16L
241743 -
241744 - Accordingly, after investing 6 hours, I conclude these capabilities
241745 - do not improve memory management for SDS.
241746 -
241747 -
241748 -
241749 -
241750 -
241751 -
241752 -
241753 -
241754 -
241755 -
241756 -
241757 -
241758 -
241759 -
2418 -