winscape 2368
This may be the next big thing in open source. Although it may be easier to address it at a protocol-service layer instead. OpenBSD has seen some of this...
1) Memory management is implemented by the programmer. The programmer is responsible for all memory management. A blue screen of rest is caused by possibly one or two things... a) Failures on part of the programmer, b) Hardware failure.
Should... I won't tell you how many times I crashed OS's because of either bad driver code or bad hardware. If...
The standard interface for DOS involves only two things. a) a keyboard, and b) an 80x25 screen. Somethings could be tweeked here and there and 80x43 and other line sizes could be implemented.
Windows 2000 does not recognize a Windows XP formatted (NTFS) file system. So the problem still remains.
Microsoft doesn't provide source code for Windows either.
PWB, VB 3.0 for DOS, VC 8.0(?) for DOS, and then there are all the current DOS command-line tools, including...
dumpbin.exe telnet.exe
At the time VB for DOS 3.0 came out, Microsoft also provided VB for Windows 3.0 (16-bit). VB for Windows 3.0 (16-bit) offered RAD methods for drawing and creating Forms (Windows).
By the way, the standard method for doing mbutt installations of Windows 9x, NT, 2K, XP and 2003 involve creating a DOS 5.0 disk, putting a DOS command-line tools onto the disk and creating a couple files called:
Of course it's a "should" :-). But TOPS-10 was seriously way ahead making that "should" a reality. That is one of the things that SMP did--provide more than one data...
AUTOEXEC.BAT, and CONFIG.SYS.
Then using one of the following files, XCOPY from DOS, from Windows 9x, or maybe even from NT (I never tested the NT or later versions with a DOS 5.0 system-formatted disk). The format.com files for newer operatings has been updated to support newer file systems. I haven't done this in a long time, but for the deployment of XP, the file used to format the drive, is still called oformat.com and doesn't run under XP. It's a DOS command-line tool, and it's possible that XP installs to a Win32 FAT and then another DOS (32-bit DOS) command-line tool is used to convert the file system from FAT32 to NTFS (convert.exe) AFTER the OS is finished installing.
Yes. If it doesn't happen, the open source isn't working. Aw, hell, TOPS-10 bias alert! I think both are needed. I'm not sure this top-down monitoring will...
As of my understanding, this is the way to pre-install Win9x, WinNT4, Win2K, WinXP and Win2003. You can learn more about it by searching for the word "preinstall" on Microsoft's website.
-- Jim Carlock Post replies to the newsgroup, thanks.
Alt Folklore Computers from Newsgroups