1. Compile C Program In Dost Remotes
2. Compile C Program In Dost Remote

A really infinite loop, counting from 1 to 10 with increment of 0. You need infinite or more increments to reach the 10. For /L%%n in (1,0,10) do ( echo do stuff rem. can't be leaved with a goto (hangs) rem.

Enables/sets international features of DOS nnn is country code (001==US) mmm is code page (437 is default, 850 is updated form, 1252 for Windows) [drive][path]file specifies file with country specific data e.g. Country=001,850,C: FDOS BIN COUNTRY.SYS DEVICE Usage: device=[d:][path]file [options] Load the device.

can't be stopped with exit /b (hangs) rem. can be stopped with exit rem. can be stopped with a syntax error call:stop ):stop call:stop 2nul:stop creates a syntax error, quits the batch This could be useful if you need a really infinite loop, as it is much faster than a goto:loop version because a for-loop is cached completely once at startup.

. 0) Preface I have noticed that many users have little or hardly any knowledge of the basic configuration topics. In the last years I have been asked very often to have a look at someone's 'autoexec', because something was not working as expected. Perhaps you have had (or still have) those problems. If you think you're an config.sys expert I would suggest you still read this document, as it contains perhaps some tricks and features you do not know yet.

In the good old days there was MS-DOS (sometimes people used PC-DOS, the clone from IBM for their pc-series. Later on DR-DOS was used for some days mainly because it was some $ cheaper.). When IBM designed their first PCs they only had the MDA textmode capability. The MS-DOS that was delivered had (and still has) relatively good support for textmode (have a look at INT10h). But some years later everybody was able to purchase graphic adapters that could display bitmapped graphics.

The PC design was not really prepared for this and most software still used textmode. But with the introduction of Microsoft Windows things changed. Microsoft presented a standard for graphic user interfaces, so nearly everybody could use the new look.

And hardware manufactores supplied drivers for their products, and soon the complete PC world only wanted Windows. (I herewith omit the fact that Win1 and Win2 were no real successes. The hurry started in 1990, when Windows 3.0 was introduced). But there was still lots of software to run on MS-DOS and people wanted to use those old software packages. So Microsoft did not program Windows as a standalone operating system (which they could have done, if they wanted), but rather as a graphical add-on for MS-DOS. Again some years later some companies shouted MS-DOS is 'out', mostly to sell their own operating systems (mainly IBM with OS/2). So Microsoft had to react.

In fact they always tell you that their product Windows 95 is a complete operating system no longer relying on MS-DOS. But don't trust them. It is all the old way! Every time you start up your Windows 95 machine, MS-DOS (in this case v7.0) is started.

Command.com then starts a file called win.com in your windows directory. If you don't trust me, then rename your win.com to some other name and reboot your machine. You will notice, that you have the classic command.com interface. If you quit windows again you will get a nice picture telling you that you can turn off your computer.

But the whole truth is, that you are now back to MS-DOS, but your graphic card is still switched to gfx mode. If you type mode co80 and press enter you will get the classic command prompt. Summary: Windows95 behaves just as Windows 3.x did and we can get some advantages of this fact. In fact Microsoft has prepared their software for the things we want to do. So at first you should rename your renamed win.com to the original name again. Then you have to go to the command prompt, either with a shell in Windows or from boot disk, or which ever way you prefer. Now we want to have a look at the file MSDOS.SYS.

Before Win95 this file was needed to boot up the machine together with IO.SYS and every computer has this file on its hard disk in the root directory. With windows 95 and dos 7.0 things changed. MSDOS.SYS is not longer a binary file. But of course it is hidden, system and protected, so at first we have to set some proper attributes: attrib -r -s -h msdos.sys no we can have a look at this file in our favourite text editor: edit msdos.sys Mine look like this: Paths Windir=c: windows Winbootdir=c: windows Hostwinbootdrv=c Options BootMulti=1 BootGui=0 Logo=0 Network=1;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; and there are a couple of; lines more to follow.

As in all Microsoft configuration files this file is seperated in sections. Each section starts with a key word in brackets. The PATHS section should be no mystery to you and you normally don't need to change it. But very interesting is the next section, the OPTIONS section. Here we find 4 entries. If some of the entries above are not listed in your msdos.sys that is somewhat normal. But you can just insert them.

UpdateStar has been tested to meet all of the technical requirements to be compatible with Windows 10, 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2003, 2008, and Windows XP, 32 bit and 64 bit editions. UpdateStar is compatible with Windows platforms. UpdateStar Free and UpdateStar Premium come with the same installer. UpdateStar includes such as English, German, French, Italian, Hungarian, Russian and. Simply double-click the downloaded file to install it. Download lagu ost film mulan.

BootMulti this option enables multiple boot configurations. Even if you only want on configuration it does not hurt to enable this option. BootGui now this is a real highlight.

Window's Setup enables this option and therefore the command processor load windows every time the machine starts. By disabling this option you will get the command line at startup and can start windows easily by typing 'win'. So disable this. Logo Many people find it totally cool to have big background and startup pictures.

I personally prefer the classic style of a black screen. This option enables the startup picture, so I disabled it. Network If you want to use Network enable this.

If you've modified the file according to your needs save it. Then exit your editor and make it protected again with: attrib +r +h +s msdos.sys Now we go a little bit deeper into the configuration. We will now handle our config.sys file. But before we edit it, we have to get some overview of what our system think it needs. The mem programm fits our needs. Type: mem /c/p my output look like this. You will later notice (when you are an expert) that the above command is the best utility when optimizing your configuration.

@echo off this line disables the command processor to disable the 'key' output. Programm output however is of course not disabled. This option is personal taste, but most people want this enabled. Verify off ms-dos has an option to check for errors while saving files. But those methods are so badly programes that they are totally useless and only eat time. So disabling this option can speed up your disk system a bit.

Set compec normally this evironment variable is set by the system, but noone forbids us to set it manually (and we have to set it when using 4dos). If you do not want to use 4DOS, leave this line out.

Set temp, set tmp set the tmp directory for your system. This option is valid for windows too. By default this is set to c: windows temp, but my D: drive is some MBs/second faster than my C: drive, so I set this value to D. I suggest you measure the speed of your hard disks (if you have more than one) and set the temp directory to the fastest drive. Be sure to create a subdirectory for temp, as the root directory of a drive can only hold 512 entries!

All other sets are system specific and you should leave them to the values you find in your autoexec. Path sets the search path for executables. Modify it to your needs prompt the basic prompt (my prompt is a little bit more complex and uses the advantages of 4dos, but i deleted it, because it is of no use here) All the above mentioned topics have only modified the internal state of the command processor. By now no program has been loaded or card initialized etc. I suggest that you order your file in the way that set, prompt, path etc.

Statements are executed at first. Then the drivers and setup programs are loaded. If you are using Windows95 you will have noticed that you can start a DOS shell from the desktop.

Starting this dos shell is a little bit different from booting your system. At first the command processor is loaded and afterwards the autoexec.bat is executed. Config.sys is not loaded at all! No here comes a problem. Because there are some drivers, setup programs etc. That do not like to be loaded inside windows (or windows does not like them to be loaded). For example I have installed two sound cards.

A sound blaster 16 and a gravis ultrasound. Now the SB setup programs can be run under windows, while the gravis software does not like to be started with windows in background. So we have to find a way to determine is windows is started.

We make this by asking for the evironment variable WINDIR. If windows is loaded it is set to the appropiate directoy, while it simply does not exist, if windows is not loaded at all.

So if you look at my autoexec.bat you see that my keyboard driver is loaded when booting my pc, as well as starting a dos shell in windows. The same applies for the initializition of my sound blaster card.

Compile C Program In Dost Remotes

But my gravis is only initialized at boot up, together with my mouse and my cdrom. When windows is running the block between the if statement and:weiter is simpy ignored. If you load a driver or a tsr program you should always try to load them into the UMB with the lh statement. In my configuration all drivers are loading 'high'. In fact you can load every dos programm high, as long as it fits into the memory left there. If dos recognizes that the program would not fit into the umb area it is loaded to conventional memory automatically, so you can not make any mistake when using this command. MS-DOS also provides the ability of multi-boot menues or multi configurations.

This option will show a nice menu at startup and you can choose between various configurations. I do NOT recommend the use of it.

Simply because I think that 99% of all users do not need multiple configurations if they set up their system properly. And those multi configuration are very hard to handle and keep up to date.

It is often easier to make a small modification to your config.sys of autoexec.bat for one boot if you need a special setup of something than installing a second boot tree and using it perhaps three times a year. Command.com is nice and working. But it is far from being cool.

I would suggest everybody to install 4DOS. It completely replaces command.com and adds dozens of new features to it.

If you have installed it once and used it for about 3 hours I bet you never want to use old command.com anymore. Watch out for another tutorial on how to use 4DOS, which I will write in the near future. Everyone owns the smartdrive program. This program is nice, but its use can be risky. If you use windows mainly you will not need this programm, since windows has its own built in file cache.

If you have loaded smartdrive and then start windows windows can not use the memory allocated by smartdrive, so the performance of windows will be infirior than without smartdrive. If you want to use DOS, smartdrive can be of use for you. But today hard disks are so fast, that the speed advantadge of smartdrive is hardly noticable for normal work.

Compile C Program In Dost Remote

Only when compiling large programs or when copying, deleting, compressing, moving many (small) files smartdrive has it's use. But be warned that smartdrive by default enables a write back technique. That means that files written to the hard disk will not be written immidiately, but rather when either the cache is full or when smartdrive thinks it would be a good time to do so. But if your system crashes, before smartdrive has flushed its buffer you will have data losses. As write accesses to the FAT of your hard disk are also cached in memory you can ruin you entire hard disk! (trust me, I had this once) Of course you can disable the write back strategie, but then smartdrive is close to uselessnes. My suggestion is that you do not load smartdrive by default, but rather from command line if you want to make many file operations (copy, delete etc).

If you have completed your work reboot your machine after a pause of 15sec (to give smartdrive time to flush its buffer). After reboot smartdrive is not longer active and you're on the save side again. This relict from times when people had very slow hard disks (or no hard disks at all) is totally outdated today and should not be used! Windows has many ways of manipulating the system core. I only suggest one here, because too much damage can be done by twiddling in win.ini, system.ini and the registry. If you want to make a new installation of windows95 go to your local newspaper dealer and buy one of those 'windows magazine' which titles every three month '100 new tricks for improving windows speed'.

Then apply all those patches and prepare your windows installation cdrom:-) The problem is, that windows is painfully slow and that you can speed up it to a certain degree. But windows is so complex, that I do not recommend those tunings. Either buy a faster pc or install a better graphical operating system (unix). But one thing: windows has always a built in file cache. Normally windows wants to handle its size, but we all know, that windows is not very clever in doing so. So we set two boundaries for windows. Open system.ini in you editor and add/modify the following three line: vcache MaxFileCache=4096 MinFileCache=1024 So windows knows that it should assign 4MB file cache maximum and hold 1MB cache whatever happens.

Experience showed, that those two values provide the best performance. If you don't trust me you can modify them, but you won't see any better difference.

Everybody knows the date when their hard disk just has some few MBs left (5MB). Now we have two possibilites.

Delete some programs or buy a new hard disk. But is it really neccessary to delete entire programs? No, but mostly you can delete lots of trash those programs have installed. Have you ever had a look how many.txt.bmp.wav.wri files windows installed in its directories? And we don't need any of them. So delete them.

The second step would be to browse through your entire hard disk and search for all readmes, fileid.diz, tmp, bak files and I am sure you will find dozens of MB of crap that exists on your hard disk. Normally you should have some close looks on every now program you install. Mostly you get many readme files you never want to read. So delete them Keep your Hard Disk tidy! Two very usefull programs. If your windows crashes daily (mine certainly does) you normally do not have to load scandisk manually, cause windows does the job for you every time you boot up again after a crash.

If you windows runs fine you should start scandisk from time to time to check for errors. Although those disk errors have reduced dramatically (I remember times from MS-DOS 5.0) they still appear from time to time. Defrag is a nice program too.

This can relocate your files physically on your hard disk. The logical directory structure is not affected by this program. This program can be run from time to time too. But you should not expect any speed increase wonders. If you have deleted many files or if you want to install a new big programm it can be usefull the run this program (after deletion; before installation), as it brings some order to your hard disk. Daily use of defrag is surely overkill.

2004-06-17 ©.