First crc thanks, it will be a great help if you can post your hdd code :) . i will only be adding read support for now ( NOTE: Not in the next release ) as i do not want people to blame us if they over write some thing. CD support is not going to be the best, there is so may variables, dvd driver do not seem to work as good as CD drive with CD's, some drives work better with CD-rw others with CD-r, no two PC seem to work the same :cry:. jas2o, to boot from a CD it emulates a floppy, to make a CD boot you get a floppy image of your OS and your burn software put it in the right place on the CD. your real floppy drive becomes your B: drive. Also once your OS is loaded weather from a floppy or a CD you can take it out of the drive and put another floppy in to load more stuff from or another CD in to play music etc. Here are the letters for drives for DexOS A:\ = first floppy drive C:\ = first Hdd drive D:\ = first CD/DVD drive There will be 2 other letters E & F at the command line you will be able to do something like this CD2 E or CD2 F This will asign the letter "E" or "F" to the second cd/dvd drive. IF you do not have a second CD driver, you will get a error message, like this: Error no second CD drive found!. For the Hdd you can do the same HDD2 E or HDD2 F Hope you get the idea :wink:.

First crc thanks, it will be a great help if you can post your hdd code Smile . i will only be adding read support for now ( NOTE: Not in the next release ) as i do not want people to blame us if they over write some thing. I posted the hdd code as a new thread. I understand your reasons not to include write support at this point. I hope it helps. The code is pretty basic, but is fairly quick and works on every machine I've tried it on from a 386 to a P4 :)

So if the cd is drive a: (becuase it is a emulated floppy) and my floppy is b:, would that mean that a: is a ram drive? Could it be a ram drive but as a: ? Jas2o BTW jas2o = Jas2o . While my username is jas2o, if it were my name I'd say it was Jas2o. (<--- That doesn't make sence doesn't it.)

Nice peace of code crc, i am amazed at the size and simplicity, i am shore it will be a big help :). jas2o, here is some info on making cd bootable, http://www.geocities.com/chrootstrap/cdrom_bootstrapping_your_kernel.html How is your programing coming a long ?. Have you done any more pascal programs ?.

I want to get into some asm but I need a few things to look at like Dex, some of Dex's code (the simple stuff :) and some more looks at the asm tut. I keep pausing pascal but go back to it every now and again. I really hope to get into some programming but I'm going to college soon (bye bye time). I was doing a pascal program. I have plans but I'm trying to find how to do something. I almost got it but I got distracted. I may get back to it soon. I'm going to disappear but i will still be here. I can still do some things they may be of any help. Jas2o BTW: I changed the forum description title from "DexOS" to "Dex - Dos Extreme".

I would get a beginners asm tut and start with dos, make a program a day even a simple one, start with a hello world, than add color, get user input etc. just keep at it, even when you think you will never get it :cry: , set your self goals and go for it, do not give up until your have got to your goal, one day it will all come together :).

Is that how you did it? So far I've been reading the ASM tut at decard. When I see a program I think of what each thing does but i'm still reading. I'll start once I get a rough idea how to do something. Jas2o BTW: This area is also a programming area now. Since projects may require questions like making it smaller, etc.

Yes thats how i started, but one thing that beginners think that can put them off, is that once you know asm you can read the code, like reading a book, but you can not, you know what each bit of the code does, but it's still not easy to understand. Even if you wrote the code, after a couple of months you find it hard to understand why we did this or put that in there etc, thats why we put comments at the side, to help us understand our own code. So the best way to learn is just keep making small bits of code, and when put together you have a great program :) . Remember the first 3 months of programming are the hardest.

Reding ASM :( It's realy hard. Writing it is much easier. Then comment everything, at least every few lines, to list what goes on in human. :wink: Then when coming back, it's not as hard to read. My only issue in ASM is which opcodes are better/faster than others to accomplish a particular task. And Brackets like to get me, I get confused... Is that the memory adress or the value at the adress? :shock: Well, Jas2o, I wrote a bootable 16-bit program a while back (floppy drive), It was a tough one, especially when I had to manipulate segments. In any case, keep learning, it's not that bad once you get a grip on it. I'm getting ready for another week fighting with USB, ish me luck. :wink:

The problem with comments is i start out writing neat code full of comments, that great if the code works like you thought it should, but if it does not, you end up cutting from here dehighlighting things and it end in a real mess :cry: , you say to yourself i will tidy that up, but you never do :wink: .

i can't live with too messy code, so the moment it works i clean it up (even if the cleaning sometimes casues new bugs).. :wink:

Yeah, I do that a lot too. Normally my comments only list what is going on on an individual line, kinda like a high level interpretation. Can get messy, though.

I have working PCI code, and now have access to the registers, working on a write routine, so I can change values. There was a line in te PCI code, right before the method returned, mov eax, NOT BIT31 , which effectively gave me the same wrong value after finding the device. I eliminated that line, and have successfully located and read the PCI registers of my USB controller. Now it's time to go to work.

Great work tonyMac :) .

I'm almost finished writing the low-level controller code. I'm going to write an app to find and configure the first usb 1 / 1.1 controller it finds. I have decided to include a debug mode to the driver, which will be available for user applications to aid their developement. I've heard that M$ has plans for such a program, but I've got the advantage of single-tasking, and not worrying about other apps trying to use the controller. :D It's actually very simple, the controller executes 1 packet, then switches a flag to 0. To send the next packet, set the flag to 1. All status of the controller is preserved while in the debug/stop state, so easy debugging. I will update in about a week, I think, unless a breakthrough occurs. 8)