Andy,

I've included my 4 source files. To get it going follow these steps:

1. Install the compiler by unzipping it to a directory like c:\assembly and then adding that
   directory to the end of your path= command in your autoexec.bat so that you can run your
   compiler from other directories. You'll probably also need to start your computer before
   this feature will work.

2. Put the source files in a directory like c:\assembly\progs or c:\assembly\hcpos and go to
   that directory in the dos prompt. Once there type "A86 hcpos.asm" This will create an 
   hcpos.com and an hcpos.sym file. The hcpos.sym file is not needed.

3. Do the same as step 2, but only for the Go.asm file and the Os.asm file.

4. Once this is done, you have all the file to my OS, you just need to get them to a disk.
   To do that you first concatenate them in the dos prompt by typing "copy /b hcpos.com + 
   fat.img + go.com + os.com final.img" This final.img file is the OS.

5. Put this final.img file onto a blank floppy disk by running rawrite.exe from the dos    prompt. Give final.img as the source and a: as the destination. Be careful not to give c:
   as the destination or you might end up having hcpos as your permanent OS instead of
   windows! - that is if the rawrite.exe author didn't take precautions to prevent this.

6. If the rawrite gives you an error like "error found on disk," it's probably not an error, 
   especially if this is after the first time you wrote the OS to that floppy. It is merely 
   dos/windows trying to recognize my format as a dos/windows one - which obviously won't
   work. If you get this error, boot in dos mode and try it because it doesn't seem to care
   about the format then.

7. Once it is successfully on disk, plug the disk in and restart your computer. The 
   instructions are EXTREMELY LIMITED so far, but if you spend a little time to see how I
   set them up, it's pretty organized and you may be able to figure it out and add some of 
   your own. Otherwise I'll be glad to answer questions.


NOTE: If you change your password or the OS itself through the source, make sure it is the same size file. My OS depends on the consistent size. This is not, however, as hard to do as you think. At the bottoms of the source I have commands like 
"AFTER_THAT      DB      380 DUP (?)"
This is simply declaring 380 bytes of null used for nothing. In the Go.asm file, I have two of these. One b/c 512 bytes is designated to usernames/passwords and some other for expansion space for the actual program. Make sure that if you add a user or something (as explained in it's directions), you subtract the right amount of bytes from the extra password space total. Every username/password entry is 33 bytes (16 bytes username + 1 byte security identification byte + 16 bytes slightly encrypted password). If you add some code to the actual OS, make sure to subtract the correct amount from the other expansion space.

Brian
oconnellb@hotmail.com