MiniVMac for Android, help needed.

About Mini vMac and all other 68k emulators, including SoftMac, Executor, and MESS.

Moderators: Cat_7, Ronald P. Regensburg

Post Reply
User avatar
24bit
Forum All-Star
Posts: 1424
Joined: Wed Nov 11, 2009 5:47 pm
Location: Germany

MiniVMac for Android, help needed.

Post by 24bit »

Got my SurfTab breeze 7.0 today from the German real store.
(real is akin of Walmart, a smaller version though)
I purchased the tab solely for MiniVMacII to have a pocket MacII to play with.
I am using the equal config as on my wife´s Y300 were everything is working, but a 4 inch screen is a pain for emulation.

MiniVMacII and MiniVMac for that matter, expect ROM and images located at /sdcard0/MiniVmac.
The SurfTab however mounts the external SD as /mnt/extsd and the emulators cant find their files.
How should I try to fix that?
SurfTabs have root access from factory.
Might be a easy fix to change the mount point of a SD card, but its way above me. :(
User avatar
adespoton
Forum All-Star
Posts: 4226
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: MiniVMac for Android, help needed.

Post by adespoton »

Probably your easiest fix is to

Code: Select all

ln -s /sdcard0 /mnt/extsd
-- this should fix this issue for all software that has the mount point hardwired.
User avatar
24bit
Forum All-Star
Posts: 1424
Joined: Wed Nov 11, 2009 5:47 pm
Location: Germany

Re: MiniVMac for Android, help needed.

Post by 24bit »

Ah, thanks for the fast reply!

Tried in SSH Terminal. ln -s /mnt/sdcard /mnt/extsd gives me an error.
link failed File exists.

My promt is "255 l app_71@android:" Does that look right?
Last edited by 24bit on Tue Dec 17, 2013 10:50 pm, edited 1 time in total.
User avatar
adespoton
Forum All-Star
Posts: 4226
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: MiniVMac for Android, help needed.

Post by adespoton »

well, another route would be to change the hardcoded path in the compiled binary.
Not being an Android user, I'm not sure how much is included in the userland software; if you can locally or remotely run a terminal, you can enter that command -- you could also do it from another device if said device can load the filesystem with root access.

I've done this sort of thing on numerous occasions with linux-based appliances and jailbroken iOS devices.
User avatar
24bit
Forum All-Star
Posts: 1424
Joined: Wed Nov 11, 2009 5:47 pm
Location: Germany

Re: MiniVMac for Android, help needed.

Post by 24bit »

Just learned from another post, that link cant work that way, as "sdcard" is the tab´s internal storage. Switching internal and external storage via vold.fstab should work however.
Hope I´m not going to brick the tablet. :)
User avatar
adespoton
Forum All-Star
Posts: 4226
Joined: Fri Nov 27, 2009 5:11 am
Location: Emaculation.com
Contact:

Re: MiniVMac for Android, help needed.

Post by adespoton »

Good to know... so what you *could* do is ln -s the actual files to the internal storage -- it would work when your external card was inserted, and fail with a broken link when it was ejected. Not the best solution, but probably the easiest, aside from actually copying the files to internal storage.
User avatar
24bit
Forum All-Star
Posts: 1424
Joined: Wed Nov 11, 2009 5:47 pm
Location: Germany

Re: MiniVMac for Android, help needed.

Post by 24bit »

Good thought!
I will try that, a script running at startup would be more convenient though.
But first things first. :)
User avatar
24bit
Forum All-Star
Posts: 1424
Joined: Wed Nov 11, 2009 5:47 pm
Location: Germany

Re: MiniVMac for Android, help needed.

Post by 24bit »

fuzzynco posted the following on xda-developers, 5th January 2012, 07:14 AM.
From what I gather its a lost case for me.
Maybe Gil Osher is kind enough to add some kind of file requester to his MiniVMac port, instead of presuming files are located at /sdcard/minivmac.
As I understand it, the /sdcard & /sdcard2 (/sdcard/ext_sd) issue is
really implemented in Ice Cream Sandwich's changes.

HTC sort of 'back ported' the idea to the newer HTC devices, hence
the problem with the Rezound.

In ICS /sdcard represents the user writable storage space
which on devices without a real sd card (like Galaxy Nexus)
give them a phoney /sdcard to write to.

The implementation, again, as I understand it, is to have a real
ext3(ext4) file system containing /data (and a subdirectory
named /sdcard), the /sdcard directory is FUSE remounted
as a redirected file system with the filtered attributes behaving like a
FAT32 file system. This is then mounted as /sdcard giving
those other devices a pseudo sd card. The problem is devices
the do have real sd cards, since the name /sdcard is already used
by the 'kludged' file system, we get /sdcard2 (or /sdcard/ext_sd or
both). While ICS does support USB Mass Storage, the Nexus doesn't
have any so it didn't, so USB MTP (Media Transport Protocol over USB)
is used to export the /sdcard file system, in ICS. I'm guessing
the pseudo-sdcard will have to be exported via MTP because
it can co-mount while mass storage has to dedicate the filesystem
to one side or the other and /data has to be available to run the OS.
The real sd card being a fat32 should still export via USB mass storage.


What HTC did for GB, I believe, is still have a real fat32 file system
(partition 32), but 'back port' the concept of /sdcard being internal
and not external space. I'm guessing the ICS OTA, when it comes,
will require a wipe, to facilitate repartitioning the internal flash,
to combine /data and /sdcard and implement the changes to support
the MTP pseudo-partition.

My feeling, is the App Dev's need to update to a more current SDK
to be aware of the changes and support an app setting to tell the app
where to look for its data, rather than assume /sdcard is an sd card.

Amazon's Kindle department told me 3.3.1.1. was supposed to address
this, but failed, so they are working on a fix for the fix. Barnes and Noble
said their Nook app also was being updated to accommodate the OS
changes.
As it is, I´m going to keep my €60 MacII, though I can only have few or small disk images on the 1GB something internal fake "sdcard".

Image
Post Reply