Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.msdos.programmer > #1410 > unrolled thread

Help w/ New OS: SGOS

Back to article view | Back to comp.os.msdos.programmer

Contents

  Help w/ New OS: SGOS Harry Potter <rose.joseph12@yahoo.com> - 2014-06-21 05:52 -0700
    Re: Help w/ New OS: SGOS "Auric__" <not.my.real@email.address> - 2014-06-21 18:21 +0000
      Re: Help w/ New OS: SGOS Harry Potter <rose.joseph12@yahoo.com> - 2014-06-21 13:49 -0700
        Re: Help w/ New OS: SGOS "James Harris" <james.harris.1@gmail.com> - 2014-06-21 22:41 +0100
        Re: Help w/ New OS: SGOS "Benjamin David Lunt" <zfysz@fysnet.net> - 2014-06-21 18:39 -0700
        Re: Help w/ New OS: SGOS "Rod Pemberton" <dont_use_email@xnothavet.cqm> - 2014-06-21 23:35 -0400
          Re: Help w/ New OS: SGOS Harry Potter <rose.joseph12@yahoo.com> - 2014-06-22 10:55 -0700
            Re: Help w/ New OS: SGOS "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-06-22 15:20 -0700
              Re: Help w/ New OS: SGOS Harry Potter <rose.joseph12@yahoo.com> - 2014-06-28 11:36 -0700
                Re: Help w/ New OS: SGOS "Rod Pemberton" <dont_use_email@xnothavet.cqm> - 2014-06-28 15:59 -0400
                  Re: Help w/ New OS: SGOS Harry Potter <rose.joseph12@yahoo.com> - 2014-06-28 13:46 -0700
        Re: Help w/ New OS: SGOS Wildman <best_lay@yahoo.com> - 2014-07-31 22:37 -0500
    Re: Help w/ New OS: SGOS Sjouke Burry <burrynulnulfour@ppllaanneett.nnll> - 2014-06-22 00:02 +0200

#1410 — Help w/ New OS: SGOS

I am thinking about creating a new OS and am looking for some basic information about the BIOS and system start-up and memory management.  Any help would be appreciated.

[toc] | [next] | [standalone]

#1411

Harry Potter wrote:

> I am thinking about creating a new OS and am looking for some basic
> information about the BIOS and system start-up and memory management.
> Any help would be appreciated.

What kind of info do you want?

Basically, power starts, BIOS gets control, it looks for the boot sector of 
the boot disk, and hands off control to that. Read here for a bit more 
details:

  https://en.wikipedia.org/wiki/Booting#Modern_boot_loaders

-- 
The food court is downstairs. The cookie stand is upstairs.
It's not like we're talking quantum physics here.

[toc] | [prev] | [next] | [standalone]

#1412

On Saturday, June 21, 2014 2:21:19 PM UTC-4, Auric__ wrote:
> What kind of info do you want?
> 
> Basically, power starts, BIOS gets control, it looks for the boot sector of 
> the boot disk, and hands off control to that. Read here for a bit more 
> details:
> 
>   https://en.wikipedia.org/wiki/Booting#Modern_boot_loaders
> 
Basically, I am looking on how to create a boot sector, communicate with the BIOS, handle RAM (in 386 V86 mode) and create a file system.  These should give me a starting position.  BTW, thank you for the link!  :)

[toc] | [prev] | [next] | [standalone]

#1413

"Harry Potter" <rose.joseph12@yahoo.com> wrote in message 
news:c1855d5e-9bff-4d9e-bd84-ace682e168ce@googlegroups.com...
> On Saturday, June 21, 2014 2:21:19 PM UTC-4, Auric__ wrote:
>> What kind of info do you want?
>>
>> Basically, power starts, BIOS gets control, it looks for the boot sector 
>> of
>> the boot disk, and hands off control to that. Read here for a bit more
>> details:
>>
>>   https://en.wikipedia.org/wiki/Booting#Modern_boot_loaders
>>
> Basically, I am looking on how to create a boot sector, communicate with 
> the BIOS, handle RAM (in 386 V86 mode) and create a file system.  These 
> should give me a starting position.

There is a good place where you can discuss such things, newsgroup

  alt.os.development

There are also some useful web sites such as

  http://wiki.osdev.org/
  http://aodfaq.wikispaces.com/

James

[toc] | [prev] | [next] | [standalone]

#1415

"Harry Potter" <rose.joseph12@yahoo.com> wrote in message 
news:c1855d5e-9bff-4d9e-bd84-ace682e168ce@googlegroups.com...
> On Saturday, June 21, 2014 2:21:19 PM UTC-4, Auric__ wrote:
>> What kind of info do you want?
>>
>> Basically, power starts, BIOS gets control, it looks for the boot sector 
>> of
>> the boot disk, and hands off control to that. Read here for a bit more
>> details:
>>
>>   https://en.wikipedia.org/wiki/Booting#Modern_boot_loaders
>>
> Basically, I am looking on how to create a boot sector, communicate with 
> the BIOS, handle RAM (in 386 V86 mode) and create a file system.  These 
> should give me a starting position.  BTW, thank you for the link!  :)


Hi,

As with the other suggestions, along with alt.os.development, might I
suggest a book?

  http://www.fysnet.net/the_system_core.htm

This book shows you how to go from the "power starts, BIOS gets control"
(Hi Auric) to a round robin type task scheduler.  It shows the boot
code, how to write the boot code, how to manage memory, how to communicate
with the BIOS, and other things needed.

It is a simplistic operating system, ready for lots of additions and
improvements, but shows you how to get started.

It also includes many utilities needed to create disk images, write
disk images, get disk information, the a20 line, etc.

Then for file systems, check out Volume 2 in that series.

  http://www.fysnet.net/the_virtual_file_system.htm

Ben


-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Forever Young Software
http://www.fysnet.net/index.htm
http://www.fysnet.net/osdesign_book_series.htm
To reply by email, please remove the zzzzzz's

Batteries not included, some Assembly required. 

[toc] | [prev] | [next] | [standalone]

#1416

On Sat, 21 Jun 2014 16:49:15 -0400, Harry Potter <rose.joseph12@yahoo.com>  
wrote:

> Basically, I am looking on how to create a boot sector, communicate
> with the BIOS, handle RAM (in 386 V86 mode) and create a file system.
> These should give me a starting position.

These two are the easier of the four:
-communicate with BIOS
-boot sector

These are a bit more advanced:
-handle RAM
-V86 mode

This can be much less complex if using BIOS
or far more complex, if programming IDE or SATA
hardware directly:
-create a file system


If you're using DOS, you can learn how to call the
BIOS using DOS .com's.  Otherwise, if using Linux
or Windows, you'll have to create a bootsector to
call the BIOS directly, or you'll have to use an
emulator, e.g., Bochs, QEMU, VMware, dosemu, etc
to execute the .com.

Which assembler or compiler are you considering?


Rod Pemberton

[toc] | [prev] | [next] | [standalone]

#1417

I recently downloaded NASM for Win32 and DOS.   I have available two Win98 computers and a DOS laptop.  The DOS laptop doesn't have a hard drive, but I'm using an external Zip100 drive as a hard drive.  The first incarnation of the OS may be floppy-based if possible.  It is not a DOS-based OS and is meant to do things its own way.  I have some ideas on how to build it.  For now, the listed items may be the first things I need to create a working OS.  I also have OW, and my DOS-based C compilers can't do the needed 386+ code.  My OS is supposed to be a 16-bit OS running in 386 V86 mode and, therefore, will require a 32-bit compiler.  Also, as it does things its own way, it will require a special executable format.  I will worry about that later.

Thank you for the recommendations!  :)

[toc] | [prev] | [next] | [standalone]

#1418

On Sunday, June 22, 2014 10:55:27 AM UTC-7, Harry Potter wrote:
> I recently downloaded NASM for Win32 and DOS.   I have available two Win98 computers and a DOS laptop.  The DOS laptop doesn't have a hard drive, but I'm using an external Zip100 drive as a hard drive.  The first incarnation of the OS may be floppy-based if possible.  It is not a DOS-based OS and is meant to do things its own way.  I have some ideas on how to build it.  For now, the listed items may be the first things I need to create a working OS.  I also have OW, and my DOS-based C compilers can't do the needed 386+ code.  My OS is supposed to be a 16-bit OS running in 386 V86 mode and, therefore, will require a 32-bit compiler.  Also, as it does things its own way, it will require a special executable format.  I will worry about that later.
> 
> 
> 
> Thank you for the recommendations!  :)

If your OS is 16-bit, you don't really need a 32-bit compiler. At most, you need some assembly code here and there. The same applies to compilers. You need to learn how to use them to get what you want and most of the time you'll do just fine if you adapt by writing some asm code or writing code to support an existing executable format. Btw, for most 16-bit things, the DOS .EXE format is good enough. For most 32-bit things pretty much any format will do, ELF, PE/COFF, a.out, etc.

[toc] | [prev] | [next] | [standalone]

#1419

On Sunday, June 22, 2014 6:20:16 PM UTC-4, Alexei A. Frounze wrote:
> If your OS is 16-bit, you don't really need a 32-bit compiler. At most, you need some assembly code here and there. The same applies to compilers. You need to learn how to use them to get what you want and most of the time you'll do just fine if you adapt by writing some asm code or writing code to support an existing executable format. Btw, for most 16-bit things, the DOS .EXE format is good enough. For most 32-bit things pretty much any format will do, ELF, PE/COFF, a.out, etc.

It *is* 16-bit, but it uses V86 mode, which is only available on 386 and up.  That's why I said 386.  Otherwise, it uses a 16-bit memory model.

[toc] | [prev] | [next] | [standalone]

#1420

On Sat, 28 Jun 2014 14:36:00 -0400, Harry Potter <rose.joseph12@yahoo.com>  
wrote:

> It *is* 16-bit, but it uses V86 mode, [...]

That means interrupts are in protected mode.

What is the reasoning behind using V86 mode?


Rod Pemberton

[toc] | [prev] | [next] | [standalone]

#1421

On Saturday, June 28, 2014 3:59:31 PM UTC-4, Rod Pemberton wrote:
> That means interrupts are in protected mode.
> 
> What is the reasoning behind using V86 mode?
> 
Well, I plan on banking parts of a running program and data into and out of Conventional and Upper memory.  Kind of like EMS but everywhere in the first 1MB of memory.  If there's another way, I'm all ears.  :)

[toc] | [prev] | [next] | [standalone]

#1499

On Sat, 21 Jun 2014 13:49:15 -0700 (PDT)
Harry Potter <rose.joseph12@yahoo.com> wrote:

> Basically, I am looking on how to create a boot sector...

This might help.
https://www.dropbox.com/s/xqrazboxujm24ap/dos5bs.zip

-- 
<Wildman> GNU/Linux user #557453
The cow died so I don't need your bull!

[toc] | [prev] | [next] | [standalone]

#1414

On 21.06.14 14:52, Harry Potter wrote:
> I am thinking about creating a new OS and am looking for some basic information about the BIOS and system start-up and memory management.  Any help would be appreciated.
>
See the link below for a complete bios listing for the
XT dos computer.
> http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=9&ved=0CFgQFjAI&url=http%3A%2F%2Fwww.reenigne.org%2Fcrtc%2FPC-XT.pdf&ei=wf6lU8_PBbSS7AaBqoDAAQ&usg=AFQjCNGTKR-nFphsH21pRvSycHxIQkhFDA&bvm=bv.69411363,d.bGE

Or google for:
IBM PC XT Tecnical Reference
which gives a lot of pdf files to scan,
with complete bios code listing.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.msdos.programmer

csiph-web