Dex4U

Dex · Post by **Dex** » Wed Jul 12, 2006 10:30 am

As in you need a fat32 formated hdd drive, ( it does not read ntfs).
There is nothing automaticly loaded by kernel, so from 2mb to how much ram you have.
Just give it from 15 to 30 mb, should be safe in 99% case.
But if you have enough ram, you can use and from 2mb to 4GB.

earlz · Post by **earlz** » Wed Jul 12, 2006 11:14 am

ok then

does fat16 work?
cause I tried testing it and it don't detect files

Dex · Post by **Dex** » Wed Jul 12, 2006 12:37 pm

Heres the run down as far as fat16 goes, first Dex4u will only delete/write to floppy drives, it can read fat32 hdd drives, and fat16 hdd drivers, but for fat16 hdd you need to load module.
You can also run Dex4u (read only) from a USB key fob, but the key fob needs to be formated fat16 ( eg: if its small than 2gb and it say file sys fat ) then its useally fat16, but its very slow.
To boot dex4u from usb fob, format as fat in windows, sys file it ( which ats dos files) put kernel32.exe + gui.dex and anyother dex files, boot in your PC and at the dos prompt type kernel32 and return, when you load from floppy it is the usb key fob.
NOTE: Your PC needs to be able to boot from usb.
So best to think of Dex4u as :
Read/write floppy(fat12) including usb floppy drives.
Read only Hdd (fat32)
Read only usb fob (fat12/16)
Read only CD ISO_9660

The read only, is for safety, i do not want people deleting parts of windows and blaming us.

earlz · Post by **earlz** » Wed Jul 12, 2006 1:53 pm

yea the read-only thing is good
what if you just had some option in the source code so that if you custom compiled it then you could try writing to/from hdd's and such(like a debug version)

also fat16 probably works on vpc then because I tried writing a text file(using tex4u) to C: but since its read-only that makes since it didn't work

btw, you got serial(COM) support?

Dex · Post by **Dex** » Wed Jul 12, 2006 7:05 pm

I will add the write code, with a note to use at your own risk.
As for serial code here some work done by a team member (viki )
http://jas2o.forthworks.com/dexforum/in ... topic=95.0
Theses in the kernel32, will need to be changed,

Code: Select all

;35 interrupt 23h <- IRQ 3
	dw unhandled_irq	           ; COM 1,3
	dw sys_code
	db 0
	db sys_interrupt
	dw 0

;36 interrupt 24h <- IRQ 4
	dw unhandled_irq	           ; COM 2,4
	dw sys_code
	db 0
	db sys_interrupt
	dw 0

For these: in "idt.inc"

Code: Select all

;35 interrupt 23h <- IRQ 3
	dw com_int           ; COM 1,3
	dw sys_code
	db 0
	db sys_interrupt
	dw 0

;36 interrupt 24h <- IRQ 4
	dw com_int	           ; COM 2,4
	dw sys_code
	db 0
	db sys_interrupt
	dw 0

And this will need adding to "Isr.inc"

Code: Select all

;-------------------------------------------------------------------------
com_int:
;-------------------------------------------------------------------------
	pushad
	push  es
	push  ds
	mov   ax,8h
	mov   es,ax	
	mov   byte [es:0xB809C], "2"
  inc	[bufpos]
  call  irq_clear
	pop   ds
	pop   es
	popad
	iret

And the kernel32 reassembled.

earlz · Post by **earlz** » Wed Jul 12, 2006 7:14 pm

that looks good
lol I'm implementing COM in my OS and I thought it'd be cool to talk between the 2(yes I'm very easily amused)

Dex · Post by **Dex** » Wed Jul 12, 2006 7:25 pm

Sounds cool, note the IR that are built in to some laptops, use the same com ports, so you can use IR from one laptop to the other using the same method.
Or even control IR gadgets, like furbys, let me know if you want the IR furby code.

earlz · Post by **earlz** » Wed Jul 12, 2006 8:06 pm

I don't have an IR so...

Dex · Post by **Dex** » Fri Jul 14, 2006 8:08 am

Here is a topic for menuet C coding, which users the same type of header as Dex4u, theres some link that may help you with Dex4u ASM to C converting etc.
http://board.flatassembler.net/topic.php?t=5483