How to grab a .device from memory?

[Vulture]

Plz help me someone with this:

I want to grab blizzppc.device from memory to a proper file. Or maybe from the BlizzardPPC firmware update file? Is it possible somehow? If so, plz show me the way! Thanks!

[save2600]

There's got to be an easier way than this that I'm unaware of, but... do you have a Deneb card or something that could be flashed to using the Lucifernin software? I'm thinking once you "grab" the virtual device, it could be flashed and then downloaded back onto your hard drive. Probably a clunky way of doing it, but there it is.... lol  

Question is, why would you need to do so?

[Dragster]

do you have a Deneb card or something that could be flashed to using the Lucifernin software? I'm thinking once you "grab" the virtual device

Are you sure luciferin can grab a memory resident device? IIRC, it can't.

Cheers,

Dragster

[save2600]

Are you sure luciferin can grab a memory resident device? IIRC, it can't.

I just went to verify, but my Deneb card is now in a different machine and I've since zapped her contents. I could have sworn I had done just that when I was playing around with the virtual usbprinter.device or whatever it's called when getting TurboPrint to work with it. Unless I'm completely off my rocker, I thought I had seen that usbprinter.device or class? in the contents of my FlashROM after everything was up and running and had Luciferin grab all the devices and classes. That was months ago, so yeah - maybe my memory is faulty  

[Vulture]

Sadly, no, I don't have a deneb. The reason I want it for some experiments I'm doing with ppc devices, can't say much yet. If anyone can do it for me, or guide me how to rip it, I owe him big!

[Matt_H]

Unless I'm completely off my rocker, I thought I had seen that usbprinter.device or class?

Not completely off your rocker
I'm guessing you saw usbprinter.class, which in turn creates usbprinter.device in memory.



Back to the original problem, the only thing I can really think of is somehow grabbing the region of memory that the device is loaded into. Scout can probably help identify regions, but the whole process might be easier under emulation.

Not sure why you'd want to do this though. If the problem is that a program/utility needs a device name but insists on a disk-based file, there are workarounds, usually involving hex-editing a config file. Works for Envoy

[Vulture]

@matt_h

thx for your reply. No, I actually need the device file itself to try some things I'm working on. Scout shows the address the device is loaded, but unfortunately there's no size info to try and grab it from address x to address y.

[platon42]

Plz help me someone with this:

I want to grab blizzppc.device from memory to a proper file. Or maybe from the BlizzardPPC firmware update file? Is it possible somehow? If so, plz show me the way! Thanks!

You can't. Or at least not easily. The devices normally are PC relative or use a custom relocation scheme to execute itself from the bootrom or after being copied to ram. This means that in 99% of the cases you will not be able to create a relocatable DOS executable from a rom content. Doobrey has spent ages in manually obtaining the relocation information for the Kick 3.1 rom to create custom roms with RomSplit and Remus.

The Deneb stores its files in original DOS Hunks in the flashrom. The bootloader then simulates the LoadSeg operation to do the relocation into fast ram. I wouldn't expect other bootroms doing this rather complex job.

[amigagr]

but piru managed somehow to split rom3.1 parts and use them as plugins in his amazing blitzkick...

[platon42]

but piru managed somehow to split rom3.1 parts and use them as plugins in his amazing blitzkick...

The boing bag updates are normal LoadSegable files concatenated into a single "archive".

I didn't say it is impossible. It just takes some good experience and skills and some time to do.

[Vulture]

@platon42

Thx for the detailed reply, I've contacted Doobrey and asked him about it and he may help me with this.


So, thx everyone!