Re: Oric Disk Manager update
- From: "Twilighte" <twilighte@xxxxxxxxxxxxxx>
- Date: Tue, 9 Aug 2005 19:27:12 +0000 (UTC)
"Simon" <nospam@xxxxxxxxxx> wrote in message
news:42f7c81b$0$7812$626a14ce@xxxxxxxxxxxxxxx
> Thanks for taking some time to try ODM! And thanks for the comments ;-)
> The next main goal would be the possibility to ADD files to the DSK. But
> this is another huge challenge - maybe in 6 years? ;-)
Not acceptable, in 6 weeks please. ;)
> Twilighte wrote:
>> When you double-click on a file whose range is A000-BF3F or uses the
>> extension HRS, HIR or SCN, the file would be displayed as an image like
>> you do in PCHIRES. An extension of this might display character sets or
>> Text screens.
>
> Problem: PCHires only displays monochrom pictures (much easier).
> If you just need to have an overview of the picture, having coloured ones
> displayed as monochrom could suffice...
Hmm, i would prefer colour. I think Jede or Dbug did something like this.
Ought to ask them.
>> 2) When you dump info to a text file, the complete file could be dumped
>> .byt style aswell.
>
> What's this .byt style?
Basically, having the option to dump the contents of a file to .h or .s text
file, so if a file contained 16 bytes of data (excluding header), it would
appear in a filename.s or filename.h as...
.byt 0,0,0,0,1,1,1,1,2,2,2,2,3,3,3,3
Values are example only.
This would be very useful for transferring Oric generated files into PC
files for compiling with machine code.
I had this issue with screens and tables i'd done in Euphoric for Pulsoid.
The workaround i did was to load the file in Euphoric, CSAVE it, then run
Dbugs HEADER utility to remove the tap header, then run another Dbug utility
to convert the binary file to a text file.
>> 3) The facility to drag/drop tap files into the disc directory from
>> explorer.
>
> Aha, double problem:
> - I have never found how drag and drop from another application was
> supposed to work with VB4 (if it ever exists)
> - I guess you mean *adding* file to the DSK, which is more complicated
> than just reading and exctracting them (see the beginning of this post)
> But that will probably be the next thing to do.
Yes, i can see that that could be a pain to get working, especially since
your dealing with two areas, populating disc with file and updating disc
directory.
>> 4) The facility to disassemble machine code files in the directory to .s
>> or .h files on the pc
>
> Wow hehe hohoho, maybe in another life ;-)
> Note that, under Windows, you have the useful little tool called
> "sadasm.exe". Exctract a file without header. Insert at its beginning 2
> bytes indicating the start address of the program. Open it with sadasm:
> the code is displayed with ASM instructions.
> I could do a special extraction format for the extracted file, for sadasm.
Not sure if this is what you are meaning, but link into Sadasm in ODM (Call
dos routine) when selected file in directory.
>> 5) The facility to perform a disk file transfer from two or more disks
>
> Mmmmh, if I understand correctly the idea, I suspect this would be much,
> much work. For the moment, keep COPY "*.*" to "B-*.*" ;-)
Yeah, the latter two are just extreme ideas, of which i have many more :]
Much respect
Twi
.
- Follow-Ups:
- Re: Oric Disk Manager update
- From: Jede
- Re: Oric Disk Manager update
- References:
- Oric Disk Manager update
- From: Simon
- Re: Oric Disk Manager update
- From: Twilighte
- Re: Oric Disk Manager update
- From: Simon
- Oric Disk Manager update
- Prev by Date: Re: Oric Disk Manager update
- Next by Date: Re: Oric Disk Manager update
- Previous by thread: Re: Oric Disk Manager update
- Next by thread: Re: Oric Disk Manager update
- Index(es):
Relevant Pages
|
