Amiga.org
Amiga computer related discussion => General chat about Amiga topics => Topic started by: the777 on January 04, 2025, 12:08:17 AM
-
so you can look at the ascii of the file... . so not actually run the file but put it somewhere in memory so i can take a look at the ascii, hex, decimal, disassembly, etc...
-
Why not use a hex editor instead, or Directory Opus?
why does it need to be Amiga Basic or "amigados"?
-
deleted
-
because i want to see if the amiga could do it out of the box
-
Copy the file to RAM: then open with Ed?
-
Copy the file to RAM: then open with Ed?
the idea is to use basic at some point to turn the decimal into colored dots to represent whats on the disk or file
-
"can you load a file into memory in amigabasic or in amigados?"
both of those things would be without purpose if they were unable to perform that function.
What a ridiculous question.
-
deleted
-
"can you load a file into memory in amigabasic or in amigados?"
both of those things would be without purpose if they were unable to perform that function.
What a ridiculous question.
the idea it to put the code into ram, so it can be read in ascii, hex, decimal, etc. not loaded into basic as a program, etc.
-
The answer is yes. Yes you can.
-
So the poster has asked a valid question. Yet it appears the Sheldon’s have appeared to take the p!
Come on guys if you know the answer to the question at least properly answer it…
I don’t know the answer, so enlighten us….
Also this poster has just joined. What a welcome! 🙄
-
One problem is the lack of information given by the OP.
There's no such thing as "a file" - at least not in any useful manner.
He needs to specify which kind of file it is and what sort of content he expects to be able to look for in the file. Then maybe more useful information could be given.
Best regards,
Niels
-
One problem is the lack of information given by the OP.
There's no such thing as "a file" - at least not in any useful manner.
He needs to specify which kind of file it is and what sort of content he expects to be able to look for in the file. Then maybe more useful information could be given.
Best regards,
Niels
i need it to read the sectors of a disk. i want to see what is in each sector and represent it as decimal numbers. im not looking for anything particular in the code. that information could be used to draw a map of the disk in color or monochrome
ive used amos to read the data inside a file and draw a color map of it but now i want to read the sectors directly
i know there is a trackdisk extension for amos but the instructions arent very good after translating from french
and i know there is an undocumented trackdisk command for blitz basic but cant find any instructions for it
-
Good description from the Op.
Welcome to Amiga.org 👍🏻
-
Yes, much better explanation, thanks.
So when you read the disk tracks directly, it's not really a file either, but of course those data that you read can be written into a file, and from there on it looks like you know what to do.
I'm not at all familiar with things like Amos or Blitz, but hopefully someone else can help more there.
Just be aware that when you read the raw data from the disk, you may often end up with chunks of data belonging to separate files, as they will often have been written to the disk interleaved with each other.
But if your aim is more or less to produce some "art" out of the data, that shouldn't be important to you, I guess.
Best regards,
Niels
-
https://aminet.net/package/util/sys/Dev-Handler
-
https://aminet.net/package/util/sys/Dev-Handler
whats that? does it work with any basic interpreter?
-
whats that? does it work with any basic interpreter?
It's what it says in the readme...
"The DEV-Handler allows easy access to raw sectors of an exec type device under the dos.library environment."
It means you can access block devices, such as floppy drives, hard drives and partitions, as if they are files, straight from DOS.
Can your basic interpreter read files? If yes, then it can also read disks and partitions.
For example, you can load a raw image of a floppy disk into your basic interpreter simply by reading in the file DEV:DF0 (or if you prefer, DEV:trackdisk.device/0)
-
@the777
All once the Dev-handler has been installed and is active, or course (just trying to help avoid any misunderstandings).
The Dev-handler, when active, is what does the magic to create a "DEV:" pseudo-device, under which your disktracks appear as files.
At least thats' the main gist of it. But do read the readme and other docs.
(Never tried it myself, but looks useful and simple if you need it).
Best regards,
Niels