@joerg

That’s the answer I think have looked for,I going try to change that…

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Quote:

I'm fared that my problem do not only extend to debug output but also, is maybe effects how I convert multi treaded IO request into single treaded IO request, I concerned because this routines look where similar.

If it looks similar it's probably wrong, all you have to do in your Dev_BeginIO() function is
ior->io_Flags &= ~IOF_QUICK;
IExec->PutMsg(task_port, &ior->io_Message);
return;

In the final version you have to do more, for example get the device/unit task port from the device or unit structure to forward it to the correct device (if you use a single task for all units of the device) or unit (if you use seperate tasks per unit) task, and usually you check in beginio() if the command is supported at all and return an error if not without forwarding it to the device/unit task, handle some simple commands like NSCMD_DEVICEQUERY directly in beginio(), etc., but for a single unit debug version of a device that's all you need.

@joerg

Well I have one task for every controller, so I don’t get lots of programs tring change hardware registers at once, every task controls two units, every tasks also checks for disk change.

Quote:

if the command is supported at all and return an error if not without forwarding it to the device/unit task

Currently every thing is forwarded to a task.

Last edited by NutsAboutAmiga on 28-Aug-2006 at 04:07 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@joerg

Success: device lockups removed…
“IExec -> Remove (msg);” where to blame, removed that.

Tow major problems reaming, and one minor problem

* CMD_UPDATE Do not always write content to disk.
This one is critical for release of the device to the public.

Maybe I should add some validation tests or some thing…
It’s where odd, CMD_UPDATE works fine when I initialise the device after quick format

* MSDOS codec is not working…
I have mostly Amiga DD disks so I don’t really care about that, some one else might.

* Minor problem, HD / DD disks are not auto detected.

Last edited by NutsAboutAmiga on 29-Aug-2006 at 09:18 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

How is the CW3 progressing?

Any issues compared with the CW4?

_________________
Site admins are people too..pooff!

@tomazkid

Oh yes almost forget about that the CW3, the module probe code for CW3 needes to be added, it needs some rewriting to be adapted to the current code, and I don’t have CW3, I think it will work out of the box but can’t guaranty that.

Last edited by NutsAboutAmiga on 29-Aug-2006 at 08:08 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Quote:

I do use timer device for some of my milliseconds delays, but I don’t know if timer.device is good for multitasking so that’s way I do use IDOS -> Delay() while waiting for NT_REPLYMSG

Using timer.device for waiting a specific amount of time is the ONE and ONLY way, everything else (busy looping, etc) is wrong. There may exist some other functions (like IDOS->Delay) , but all these are based on timer.device.

_________________
Why stop it now, just when I am hating it?

Thore Böckelmann

@tboeckel

Quote:

I do use IDOS -> Delay() while waiting for NT_REPLYMSG

I have removed all that, now my debug program, just frees up the shard memory and waits for next message, the sender do no longer wait for receiver to finish whit the debug messages, no ReplyMsg() required for debugging, and my understand is that GetMsg unattached the message so there no other cleanup code needed ether.

I believe that I removed waiting for NT_REPLYMSG on device IO too, should not really be needed, now that IExec -> Remove() is no longer used, and really it’s the filesystem that should be responding to replays not my device driver.

Last edited by NutsAboutAmiga on 29-Aug-2006 at 02:51 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@tomazkid

For the record the CW3 module probe code is added.

(I have not found out way writing to floppy do not always work yet)

Last edited by NutsAboutAmiga on 31-Aug-2006 at 02:58 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Looking forward to the first beta later on

_________________
Site admins are people too..pooff!

@NutsAboutAmiga
Yes ;o)
A first public beta please ;o)
For my new MK4
Bye HUNO

_________________
AmigaOS 4.1 Rulez
X5000
And X1000

@HunoPPC

He told me a while ago that he would release it when all critcal issues was fixed,think that it stands still. I'll whip him a bit for you so progress moves faster. hehe

_________________
I'm an antique. Don't light my fuse

@NutsAboutAmiga

I have a CW3 and would be happy to test for you.

Regards,
        JCC

@Antique
Yes ;o)
It would be although it accelerates because my D7 start to mildew ;o)
Bye Huno
Thanks ;o)

_________________
AmigaOS 4.1 Rulez
X5000
And X1000

@HunoPPC

You are new member .

I can upload the current driver whit out write support, but I’m not going to upload some thing where write do not work most of the time, and some times works fine, I only going to get useless bug reports, complaints.

What I need is some one that know the hardware to help me whit
TD_FORMAT / TD_UPDATE issues (cw_write).

I’m wondering if the data is written but to the wrong location, if maybe seek fails, maybe it’s just some register values that needs to be set, maybe I’m using wrong timing when I write a track.

Maybe I should try rewriting the Linux kernel code again…

Best regards
Kjetil Hvalstrand

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga
Thank you for "the new member"
I propose as Betatester if you want to advance the project ;o)
Thanks you for this developpements
Good work
bye huno

_________________
AmigaOS 4.1 Rulez
X5000
And X1000

@All

Yesterday I started cleaning up the source code for the first public Alfa version…
It’s where likely that writing will be disabled, what I need to do is write some documentation for callback hooks API that I have written and some other Information that’s normal.

I have also secretly started rewriting my web page, the current one is hope less to maintain.

All my successful and unsuccessful projects will be hosted there, I think about adding a paypal account, and you’re all welcome to give me feedback on what unfinished project you like me to be working on in the future, I have lots of unfinished project

Last edited by NutsAboutAmiga on 11-Sep-2006 at 02:05 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga


Hi, did you get any help from jens schoenfeldt
from individual computers?

_________________
- AmigaX1Ooo with OS4.1FE // CD32/SX32Pro/SX1/CD32Shuttle
- A600-Vampire600 FPGA // A4KT/CSPPC233,144MB,PCI, AOS4.1.6FE
- MACmini 1.5GHz // Pegasos 2 1GHz // Efika
- ATARI Falcon/060/SuperVidel // ATARI Falcon MK X

@zErec

No I did not ask

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Quote:

by NutsAboutAmiga on 11-Sep-2006 3:32:36 @All Yesterday I started cleaning up the source code for first public Alfa version& Its where likely that writing will be disabled, what I need to do is write some documentation for callback hooks API that I have written and some other Information thats normal.

That would be OK as being able to read the floppys directly is more important than being able to write to them. And the sooner the better...

_________________
--
-=#Val#=-
Valiant@Camelot


Amiga 1000; Amiga 2000; Amiga 3000T; CD-TV; CD32;
AmigaOne-XE 800Mhz G4;Sam400ep 666Mhz;
AmigaOne X-1000 1.8Ghz PA6T-1682M