Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!sm.unisys.com!oberon!orion.cf.uci.edu!paris.ics.uci.edu!bonnie.ics.uci.edu!posert From: posert@bonnie.ics.uci.edu (Bob Posert) Newsgroups: comp.windows.ms Subject: Re: Try calling your app "DISPLAY.EXE" Message-ID: <959@paris.ics.uci.edu> Date: 22 Nov 88 05:50:12 GMT References: <1281@helios.ee.lbl.gov> <453@gold.GVG.TEK.COM> Sender: news@paris.ics.uci.edu Reply-To: posert@bonnie.ics.uci.edu (Bob Posert) Organization: University of California, Irvine - Dept of ICS Lines: 32 In article <453@gold.GVG.TEK.COM> John Schultheiss writes: >In article <1281@helios.ee.lbl.gov> mikec@ux1.lbl.gov (Mike Chin) writes: >@Try renaming a window app to "DISPLAY.EXE", and then >@ [...] > >Rule # 2. When in doubt, check the .DEF file. In general, applications will >exhibit strange behavior whenever the NAME in the .DEF file does not match >the name of the application's .EXE file. >[...] If what you meant was that you changed >the names of all the source files, changed the makefile's contents, and the >.DEF file's contents to reflect these other changes, then there must be some- >thing unique about the name DISPLAY.EXE name, which is certainly a possibility. This piqued my interest, so I ran strings on win200.bin. Part of the list was: SYSTEM.DRV KEYBOARD.DRV MOUSE.DRV DISPLAY.DRV SOUND.DRV COMM.DRV FONTS.FON OEMFONTS.FON GDI.EXE USER.EXE MSDOSD.EXE MSDOS.EXE KERNEL Renaming an executable to any of these followed by .exe (e.g. oemfonts.exe) yields a file that windows will not run. I used calc.exe for my tests. Even a slight variation yields a file that will run; windows will run both msdosc.exe and msdose.exe, but not msdosd.exe. When I renamed calc.exe to msdos.exe and double clicked on it, I got a regular ms-dos window. This seems reasonable, but unexpected. --Bob -- Bob Posert I'm: posert@bonnie.ics.uci.edu or {sdcsvax|ucbvax}!ucivax!bonnie!posert Here's good luck to the pint pot, good luck to the Barley Mow. Jolly good luck to the pint pot, good luck to the Barley Mow.