Related
this from rad131304 not me, thank you
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (www dot cygwin dot com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
1. make sure your NC is disconnected from you computer
2. make sure your SD card is mounted on your computer (readable/browsable in explorer)
3. Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
4. download nooter at http //www dot mediafire dot com/?hugt8uxcfffpdvg
5. extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
6. Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
7. Select "Disk Management" under storage
8. note the drive letter of the SD card and the disk number
9. Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
10. At the prompt, type (WOQ): "mount //./<f>: /dev/sd<c>"
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
11. press enter - there should be no output
12. at the prompt, type (WOQ): "dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>"
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
13. remove the sd card from the computer and plug it into the NC
14. power down the NC (hold power button for 15 seconds)
15. connect the NC to the computer
16. Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
17. Wait for 15 seconds after the recognition
18. power down the NC
19. remove SD card ***
20. Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
21. Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
22. save the file and close
23. find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
24. add (WOQ) "0x2080" on its own line
25. power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
26. Go To: Start > Devices and Printers
27. Right-click on Nook and select properties
28. Select the hardware tab
29. If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 38
30. Click on "Nook"
31. Select Properties
32. Click Change Settings (may require UAC elevation)
33. Click update driver
34. Select "browse for driver software on your computer"
35. Browse to the android-sdk/usb_driver folder
36. click next
37. You should be done; skip to 47 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
38. If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
39. Select Properties
40. Click Change Settings (may require UAC elevation)
41. Select the Driver Tab
42. Click Uninstall
43. Click OK
44. Disconnect NC
45. Reconnect NC
46. You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
47. Go To: start > run > cmd
48. type (WOQ): "cd <path_to_android_sdk>\tools"
49. type (WOQ): "adb.exe kill-server"
You should get something like:
* server not running *
50. type (WOQ): "adb.exe remount"
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
51. You are done configuring to sideload
From here you should be able to sideload from ADB.
by rad131304
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
I believe it was mentioned in a previous post that if you did a factory reset (power off completely, then hold power, nook button and vol up) that it would reset the Nook back to non rooted factory defaults. Can anyone else confirm this?
HeroHTC said:
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
Click to expand...
Click to collapse
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
believe this was done on win 64, some buttons are located in or below menu bar, some will depend on launcher.
I also wanted to mention this
http://forum.xda-developers.com/showpost.php?p=9517050&postcount=863
NOTE: I have not even opened my nook box yet, its still sealed but I am getting ready. Just waiting on an email solution.
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
The back and menu buttons are soft-buttons. The nook for some reason hides them by default in a bunch of apps.
sudermatt said:
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
Click to expand...
Click to collapse
IIRC, somebody said that in the big thread, too.
oakleyrdc said:
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
It could be hidden (so you'll have to change the hidden files and folders setting), or installed in another user directory (like Admin).
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
I did mine on Win 64bit using winimage. Everything is working fine.
rad131304 said:
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
Click to expand...
Click to collapse
XP
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
plus 1 for XP
So once your rooted, do you need to do anything special to install apk files that you download from dropbox? Is superuser ready?
i cant find the android_winusb file in the windows XP version of the android SDK. is there a different one that does the same?
EDIT: it appears the sdk is not split between versions of windows
im going to reinstall the sdk and see maybe if i accidently deleted it at some point
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
Very little changes; the only thing I can tell you off the top of my head is that
C:\users\<username>\.android\
Becomes
C:\documents and settings\<username>\.android\
Also, I don't know where, besides device manager, that you could locate the nook like you do in devices and printers - it may show up in my computer, also in scanners and cameras in the control panel - you can always right click a drive, select properties, select the hardware tab, select the b&n storage device, click properties, select the driver tab and uninstall from there....
HTH
EDIT: To delete the NC through device manager:
start > run > compmgmt.msc
browse to Device Manager
Expand Universal Serial Bus Controllers
Select USB Mass Storage Device (there may be multiple)
Right-Click and select "properties"
select the details tab
in the dropdown, select "Hardware Ids" - if this says "USB\VID_2080&...." then this is the NC
click ok
right Click again and select uninstall
disconnect NC from computer
reconnect NC to computer
NC re-finds all drivers, including ADB
start > run > cmd
cd <android-sdk-dir>\tools
adb.exe remount
Fixed instructions!
that's what I get for writing this crap at 1 in the AM ... I left out two INSANELY important steps at step 11.
SORRY!!!!
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (http://www.cygwin.com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes or a code block, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
make sure your NC is disconnected from you computer
make sure your SD card is mounted on your computer (readable/browsable in explorer)
Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
download nooter at http://www.mediafire.com/?hugt8uxcfffpdvg
extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
Select "Disk Management" under storage
note the drive letter of the SD card and the disk number
Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
At the prompt, type:
Code:
mount //./<f>: /dev/sd<c>
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
press enter - there should be no output
REMOVE SD CARD FROM PC
INSERT SD CARD INTO PC
at the prompt, type:
Code:
dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
Click to expand...
Click to collapse
IF THIS COMPLETES ALMOST IMMEDIATELY, YOU PROBABLY HAVE AN ERROR
remove the sd card from the computer and plug it into the NC
power down the NC (hold power button for 15 seconds)
connect the NC to the computer
Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
Wait for 15 seconds after the recognition
power down the NC
remove SD card ***
Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
Code:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
save the file and close
find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
add (WOQ) "0x2080" on its own line
power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
Go To: Start > Devices and Printers
Right-click on Nook and select properties
Select the hardware tab
If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 40
Click on "Nook"
Select Properties
Click Change Settings (may require UAC elevation)
Click update driver
Select "browse for driver software on your computer"
Browse to the android-sdk/usb_driver folder
click next
You should be done; skip to 49 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
Select Properties
Click Change Settings (may require UAC elevation)
Select the Driver Tab
Click Uninstall
Click OK
Disconnect NC
Reconnect NC
You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
Go To: start > run > cmd
type:
Code:
cd <path_to_android_sdk>\tools
./adb.exe kill-server
You should get something like:
* server not running *
Click to expand...
Click to collapse
if adb.exe is not in tools (or tools does not exist), try:
Code:
cd <path_to_android_sdk>\platform-tools
./adb.exe kill-server
type:
Code:
./adb.exe remount
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
Click to expand...
Click to collapse
You are done configuring to sideload
From here you should be able to sideload from ADB.
To sideload an app, simply do the following:
Code:
./adb.exe install <app_name>
Thanks Rad!
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
When you updated the SDK, did you install the USB drivers also? If you did, that file should be in whatever directory you installed the SDK in under the usb_driver subdirectory.
cabbieBot said:
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
Click to expand...
Click to collapse
I'm an idiot, I was certain the USB Drivers were installed. Done and done now, sheesh what a waste of time!
now to hunt for adb_usb which is being a pain to find too. Has anyone found adb_usb on XP?
I can see the folder C:\documents and settings\<username>\.android\ but theres two folders in there for AVD and AndroidDesktopNotifier. Maybe if someone can upload the adb_usb file I can just throw it in the folder and cross my fingers?
Zen's Backtrack 5 For HD2 (and other) Android Smartphones
V0.3
----------------------------------------------------------
New app for loading this (and other) Linux Systems! - https://play.google.com/store/apps/details?id=com.linux.autoloader
Image and app support can be found here --> http://www.zenfulapps.com/
Packed - 640mb
Unpacked - 2.6gig (fits on 3.3 img now.)
--GRAB THE UPDATED SCRIPTS ATTACHED TO THIS POST, THEY ARE NOT PACKAGED INTO THE ZIP--
--Scripts are set to load from EXT4 partition, when i modify them for the .img's ill add them to the script pack--
--if you have .img mounting scripts from previous versions, they will work, as long as file names and directories match--
V0.3 Download
http://www.zenfulapps.com/Android/backtrack5-0.3.7z
(MD5 is still the same
MD5sum (of .7z file) - 9a4796f0ed96e03579c2b4a684d026f5
--------------------
Script pack contains
--------------------
btgo - mounts BT5, and askes how you would like to start, CLI or VNC
bts - stops BT5, and unmounts everything for it.
btl - used to login to bt5 after it has been mounted, to avoid all those "resource busy" messages
mkcore - directory installation and swap file creation
-------------
What you need
-------------
Rooted Android Smartphone
Linux on PC
Busybox installed on your device
SDcard adapter or reader, if neccesary
----------
Lets begin
----------
There are 3 different ways you can do this:
1. Fresh install on EXT4 Sdcard partition ( I HIGHLY recommend this method if possible, much better, a bit faster (no double loops to write to)
2. Create Fresh .img
3. Replace old BT5 system .img
=========================================
1. Fresh install on EXT4 Sdcard Partition
=========================================
This portion of the guide is to install BT5 on a FRESH EXT4 partition on your SDcard. Throughout this porcess, you will:
Backup your current sdcard (EVERY PARTITION, this is why we use PC-linux and not windows)
Fully erase and repartition your SDcard
Replace Android system and user data
Install BT5 on third partition
prepare system for chroot and VNC connection
----------------------------------------
Boot into your Linux operating system. **I DO NOT recommend using virtualbox or vmware, as drivers for usb and SDcard connections arent direct, things can go wrong.**
Shutdown your phone, and remove your SDcard. Do not use adb, or any other tools to do this.
insert your SDcard into your computer (adapter or reader yada yada) and mount every partition.
Make careful note of what is on which partition. safest way to back everything up is through the command line with the command
Code:
sudo cp -Rfvp /media/your-sdcard-partition/* /where/your/backup/folder/is
Do this for each partition, whether you have 1, 2, 3, or more.
In my case, my backup directory looks like this:
Code:
[[email protected] sdcard-backup]$ ls -l
total 12
drwxrwxr-x. 2 hookup-cellular hookup-cellular 4096 Sep 13 18:48 ext2
drwxrwxr-x. 2 hookup-cellular hookup-cellular 4096 Sep 13 18:48 ext4
drwxrwxr-x. 2 hookup-cellular hookup-cellular 4096 Sep 13 18:48 fat32
(ignore the empty directory sizes, my TRUE backup folder is MUCH more vulgar and i wont display it publicly, people may tear thier eyes out )
After everything is backed up, open your partition manager (in Gnome it is gparted, cant remember the name in others)
Navigate to your SDcard, and DELETE every partition. every one.
afterwards, recreate them using this strategy:
partition 1 - FAT32 size = total sdcard size minus ext2 and ext4 partition sizes
partition 2 - EXT2 size = 256mb, 512mb, 1gb, depending on how you like your apps2sd
partition 3 - EXT4 size = size you want for linux, minimum should be 4gb (mines at 10gb, i like my linux and got 3 different ones on it at the same time.)
When you are done, copy back your fat32 and ext2 stuff using the SAME COMMAND AS ABOVE (sudo cp -Rfvp from/here to/here)
Now, unzip/tar the .tar.gz package. I recommend extracting it to your pc before trying to put it on your sdcard.
Using the copy command above, put the extracted files onto your sdcard's EXT4 partition.
Double check the partition (navigate to it in nautilus or whatever filemanager your using) and ensure that it has the system copied over properly. You should see /boot /etc /root /sys so on and so forth, NOT just one folder with all of those inside of it.
Insert your SDcard, power on your phone, go to terminal emulator, and enter this:
Code:
su
cd /sdcard/scripts
sh mkcore
Swap file is damn near neccessary if your planning on using any GUI tools (armitage, zenmap)
Your directory structure is now in place, swap file created, and you start BT5 by typing (from /sdcard/scripts OR /data/linux):
Code:
sh btgo
=================================
2. Fresh Image Creation
=================================
for this, we use the dd command and mkfs.ext4 command.
Code:
dd if=/dev/zero of=/path/to/where/you/want/the/img bs=1M count=3300
Change this command as needed, running it as is wont do anything good. Change the of= to where you want your img to be located.
next is mkfs.ext4
Code:
mkfs.ext4 /path/to/where/you/want/your/img
select yes when it cautions about "not a block device"
When this is finished, mount it using these commands:
Code:
su
-your password-
mkdir -p /mnt/bt5img
mount -t ext4 /path/to/your/img /mnt/bt5img
now, extract the BT5 package to a place on your Computer. When finished, run this command:
Code:
sudo cp -Rfvp /path/to/bt5/core/* /mnt/bt5img/
changing parameters accordingly.
After this, copy the .img to /sdcard/bt5 and run the start scripts from your terminal emulator.
================================
3. Replace Existing Image
================================
Mount your bt5 image, erase what is inside of it, and copy in the new system:
Code:
su
-your password-
mkdir -p /mnt/bt5img
mount -t (your ext type) -o loop /path/to/your/bt5/img /mnt/bt5img
rm -Rfv /mnt/bt5img/*
cp -Rfvp path/to/bt5/core/* /mnt/bt5img/
unmount your .img, place it on your sdcard, and your all set.
==============================
Changes in v0.3
==============================
- Trimmed alot of fat, fits inside of 3.3 image now, though space is SEVERLY limited (removed CUPS and sound stuff, who needs to print from within thier phone anyways?)
- various small changes for performace improvements.
- a few new tools installed, but not tested
- restored my personal version that i nuked. It works now.
NEW STUFF TO COME, STAY TUNED!!!
First off, My apologies for starting a second thread on this, I've made ALOT of changes and i feel the first thread is dead and useless. (Reprimand me if needed
-pics coming once I find my camera could be a small while-
---------------------------------------
Backtrack5 for HD2 - v0.2
Customized by z3n
My goal: the perfect stealth
tool in your pocket
just one tap away
---------------------------------------
========================
Codename
Squeaky Wheel
========================
Updated, check second post for changelog
========================
DOWNLOAD
========================
Please use the scripts attached at the bottom of this post instead of the packaged ones, and i havent had a change to update the full image zip with it (uploads take a while )
V 0.2
Part 1 - http://www.megaupload.com/?d=D0MQVAS4
Part 2 - http://www.megaupload.com/?d=M2MRYLAH
MD5 - 06225e18cdbfee6f88daf7e9ee3a1163
SHA1 - eeba19e53565a1643703cf8938be2f8cfc12db9a
V 0.1
Part 1 - http://www.megaupload.com/?d=83B22Y00
Part 2 - http://www.megaupload.com/?d=SB98AA19
mirror - (NOT interchangeable)
Part 1 - http://www.megaupload.com/?d=HU320Z81
Part 2 - http://www.megaupload.com/?d=QN9C560Z
Checksums of bt5.img
MD5 = 863e6db99e5207a81ad0df7d13998235
SHA1 = c84d8f27df8b9b51059e5a6b09e65853f11de970
7zip required to extract.
Just over 1gb packed, unpacked is 4.9gb.
========================
INFO
========================
This is my first release of a customized, working, mostly stable BT5.
Many things have been added, taken out, and configured to be used within the Android system. For a full list, please see the bottom of this post.
Mounting is different than most other linux .img installations, allowing for a full (and expandable) image.
V 0.2 Now has a swap file created when you run the mkdirectory script. This swap file is necessary, as with all my tests, When you run VNC with most of the major tools, there's a high chance of the phone running out of memory (im running no extra apps, completely stock Hyperdroid)
(if you have a swapfile already, you can say no to creating another, just make sure that the file is located at /data/bt and named btswap.)
**This image is in ext4, make sure your kernel supports it!**
**Everything tested on Hyperdroid-CM7 by pongster**
==============
INSTALLATION
==============
You need:
-Full Nandroid Backup in case something goes batty
-16gb HD2
-ext4 support on your ROM/kernel (lost my ext2 image due to my own stupidity, will create another matching one later)
-Linux on PC (to create the ext4 partition)
-Busybox (from market)
-VNC Viewer (from market) (optional)
FAT32/EXT4 Split card
---------------------
1.
Back up your HD2 and SDCard to safe places (off of the phone and sdcard)
2.
Boot your linux installation and open partition manager. erase all the partitions on yor SDcard. Then create them in this order.
1. FAT32 - size of this is total sdcard size minus 6.5g (for bt image) minus 100mb for aps2sd
2. ext2 - 100mb
3. ext4 - 6.5 gb
3.
Copy the bt5.img to the root of your third partition.
copy the bts folder to the root of your FAT32 partition.
4.
if this is your first time using this script/image, run the mkdirectory script first with
Code:
su
sh /pathtoscripts/mkdirectory
Load up your android terminal and type
Code:
su
cd /path/to/scripts
sh go
5.
Now it asks you if you want to log in to the console or start vnc automatically. (check log for port, usually 5901 or 5902)
DEFAULT VNC PASSWORD IS: toortoor
DEDICATED SDCARD
----------------
Same as everything above, minus the FAT32 partition.
"sh ded"
starts for dedicated SDcard instead of
"sh go"
Proper Shutdown Procedure
=====================
Stop script has been modified to shutdown backtrack and all of the (usual) programs that stop things from unmounting properly.
Exit any VNC connection you currently have.
1. Run sh stop (from your scripts location)
2. Reboot phone as a precaution.
One thing i did personally to make this easier was load the scripts onto /data/bt, so switching SDcards or locations doesnt matter.
(I also changed the terminal start directory to my scripts folder easy quick access)
=======================
Main Features I've gotten to work
=========================
-Clean mount/umount, as long as VNC and MySQL are killed BEFORE exiting the chroot - stop script kills these now
-Apps no longer disappear for good with sdcard removed, only disappear until SDcard is reinserted (apps2SD/loop device problem, any ideas?)
-MySQL for metasploit
-Metasploit working
-Armitage working, missing some "Attack" options (looking into it)
-Zenmap installed
-OpenVPN installed
-Traffic analysis possible with tcpdump (local only)
-Enables possibility for FakeAP attacks
-macchanger works (kinda, phone needs a reboot for original MAC to return)
-Armitage Launcher placed on Desktop (takes a while to load, be patient)
-Terminal Launchers in various places (updating may randomly remove your terminal, synaptic placed on desktop as standby to redownload terminals
-guake installed (drop down Terminal, makes commands easier to see while working) (not configured to a key yet)
This probably works with other Android phones too. If you change the scripts, and as long as it has a external SDcard you can partition.
if your using a different phone, this is untested unless specified otherwise.
-boot and shutdown scripts run clean as long as VNC and MySQL are shut off(in almost all cases)
@ XDA
http://forum.xda-developers.com/show....php?t=1152994
PASSWORDS
------------
MySQL - user: root pass: toor
VNC - User: root pass:toortoor
sys pass - user:root pass:toor
(I know, standard ones, but this should answer a few questions)
===============================
Thanks
===============================
anantshri - for the original scripts and BT5 img for android
BT dev team - (of course )
and all of you
===============================
Information, bugs, and oddities
===============================
One important thing, While performing heavy operations, its normal for your screen to not turn on for a while if it turns off. Dont panic, just give it some time to finish whatever you were running and your phone will be back to normal again. DO NOT PULL THE BATTERY UNLESS ABSOLUTELY NECESSARY.
To avoid this, get wakelock (known to cause problems) or set your screen timeout to some large number.
Swap file will help with alot of this.
These are the features I've tested out so far.
No major changes to anything, (except new packages) just configuring everything i see.
If you find anything you want added in or that is acting odd, please let me know. Same goes for if you fix something!!
Overall
-------
-Repo's activated, most things work (upstart processes fail, for now)
-startvnc and stopvnc no longer give that pesky USER error
-startvnc starts mysql database for metasploit
-stopvnc stops mysql (mostly, invoke ps -A and look for mysqld. Kill it with fire(-9) if need be)
-network traffic is capture-able with tcpdump, with wifi hotspot activated
-working on adding in a swap partition on sdcard (if possible)
-openoffice installed
-openVPN installed (the quieter you become...)
-Removed Zoho Web services
MySQL
-----
default user - root
default pass - toor
-Starts automatically with startvnc
-stops automatically with stopvnc
-start manually by invoking "mysqld"
-Only runs as root (for now)
-Console hangs when it is manually loaded or shutdown, service continues running though. killall --signal 9 mysqld if needed.
Metasploit
----------
-Loads up alright (45-90 seconds)
-MySQL already set as default DB
-Must manually connect to MySQL DB each instance of metasploit by invoking (from msf) db_connect root:[email protected]
-working on a possible way to limit cpu consumption to prevent system hangs(cpulimit does some nasty things)
-So far, this is the only connection string ive been able to get to work: root:[email protected]
Armitage
--------
-Takes forever to load (30 seconds for connect screen, 4 minutes or so for main client)
-Causes system hangs frequently (to minimize this, leave the vnc server on your screen, and set the display timeout to 10 minutes-switch it back when done to conserve battery life)
-So far, this is the only connection string ive been able to get to work: root:[email protected]
-Can Crash phone if running too big of an operation (Max Phone memory problem, fixed in v.2 with swapfile added)
Zenmap
------
-Slows phone down (incredibly bad with more complex scans, of course)
-Some Complex scanning options can crash phone (Nothing damaging has happened)
-will attempt to throttle cpu usage in the future
-Can Crash phone if running too big of an operation (Max Phone memory problem, fixed in v.2 with swapfile added)
Aircrack-ng suite
-----------------
-Aircrack-ng works
-Airodump-ng doesnt work (needs monitor)
-Airdecap-ng untested
-Airdecloak-ng untested
-Airbase-ng doesnt work (needs monitor)
-Airmon-ng doesnt work (needs monitor)
-Aireplay-ng doesnt work (needs monitor)
-Airdriver-ng doesnt work (yet)
-Airolib-ng works (doesnt do anything yet)
-Airserv-ng doesnt work (needs monitor)
-Airtun-ng doesnt work(needs monitor)
Plus lots of stuff for the future, stay tuned!!
http://forum.xda-developers.com/show....php?t=1152994
In the future
=========
-nessus
-Booting via HD2 Toolbox by d4n14l (sp?)
-Custom kernel (WAYYYY down the road, but working on it)
and more
--Copyrighted by z3n, 2011
(just kidding, but it looks good )
Looks good will give it a go.
Thanks for sahring
I we could get our wifi card into monitor mode --> awesome!!!!
Thanks to z3nful & everyone made this possible!
Enjoy everyone
The next release is going to be faster, stabler, and more useful
I'm also working on a round-about way for packet injection and monitor mode
Stay tuned
Sent from my Hyperdroid Pocket Laptop
cool.. good job man..
Are you trying to patch the wifi drivers ? =D
Holy crap.....this is a dream in the making Bring on monitor mode and packet injection
I've done some researches.. and found out that many devs have tried making the driver to work on the Monitor mode.. but they failed to do that.
It looks to me that Backtrack on HD2 is kinda useless.
Not useless, just last night I ganked my roommates computer with my phone
As far as monitor mode and injection go, sadly, they may be right that its not possible, but I got some ideas that may make it work, I just need to hammer out some kinks in BT first
And who needs monitor when you can fakeAP?
"Make them hand you the keys and you don't have to break their Window(s)™"
Sent from my Hyperdroid Pocket Laptop
A m a z i n g
Next release is going to be even better this 5gig image is almost full, so I'm going to expand it to 6gig, along with instructions on how to expand your own image if that's to large or want even more space.
Btw, Wine should be good to go in the next one
stay tuned!!
Sent from my HD2 "Pocket Laptop"
I would love to see some Sceenshots (or better: a video) here!
Lol will do, gotta go find my 10 year old Polaroid I've been using this phone or all my pics and videos, so this could be tricky
Sent from my HD2 "Pocket Laptop"
good to see development beyond just starting up the image... I would be taking some pointers from here for my device too....
hope you don't mind that....
Not at all, I've been trying to track down your name again so it can add you to the credits part, as the basis of the scripts was yours lol, I just changed the loops and mounting structures around a bit, and added some stability checks.
The scripts for this image are slightly out of date but I got new ones going up once I have time they should fix a few of the small eerrors people get while mounting
My next version is a little ways out (works gotten crazy busy lately) but it'll be out eventually
Sent from my HD2 Pocket Laptop
Not Booting!
Hi Thank you for sharings this up!!! this is like a dream for alot of people.
i have followed all your steps but i have a problem when i run the scripts, the folders dont get created because when i run go i get a bounch of folder not found.
my SD card had some differences is a 16GB
with
Fat32
Ext-sd/ EXT2 -->1GB
EXT3 --> 100MB
EXT4 --> 6.5GB
could this setup causing the script to look on the wrong partitions? i have alot of time with out playing with Shell scripting but i would like to know if that is the place i should start looking for a fix
-edit- just double checked (forgot scripts were on my phone... its been a long week lol) and you should just need to change the mount -t ext4 /dev/block/vold/179:3 to /dev/block/vold/179:4
Also, did you run the new mkdirectory script? If you have the one packaged with the image its out of date. The attachment on the fist post has the updated ones
Ignore all mmcblk's
For another "buffer" partition, you need t point the sdcard parts (mmcblk0p* and vold/179:*) to what yours are in /dev/block. In your case I think you just need to change any vold/179:3 to 179:4. If you go to /dev/block/vold it will have folders from each partition (they are numbered 0 and up, but 1 would be your fat32, 2 is ext2 so on and so forth)
When I'm near my computer ill figure out the full ones for you
Sent from my HD2 Pocket Laptop
can I get it for Htc desire..??
It should work, as long as you have a big enough sdcard, your phomes kernel suppers ext4, and you might have to change a few small variables
Sent from my HD2 Pocket Laptop
Okay so I didnt really come across alot of central material on how to do this with Nook or if it even could. Since storage capacity is an issue most HD content is probably not going to be getting stored on most users tablets. I would guess that alot of users already have lots of content on their personal computers. If you have a decent wireless router configured correctly it shouldnt be a problem to be able to stream this content to the nook. The nook tablet has a decent amount of ram and the cortex a9 is more than sufficient to stream, so i was bored and figured id give it go.
What you will need to do this
Rooted Nook Tablet 8gb or 16gb shouldnt matter - for documentations sake im running aokp milestone
Personal Computer with somewhat organized media structure
Hanewin NFS Server Easy to setup in windows
BusyBox Installer Latest version of BusyBox - BusyBox Installer is what we used
MX Player seems to be the best android video player ive come across
Neon Codec is compatible with our processor and is necessary for decoding files with dts audio
Its important to organize your movies into a single folder if possible to decrease on mountpoints. If you must use different folders, try and name them movies1 movies2 movies3, etc
After organizing download and install hanewin. Make sure UPnP is enabled on your router it saves you from having to fwd ports later on.
Open Hanewin in the general tab uncheck UDP and check version 2 and 3, and check TCP.
On the server tab, Check "allow mount of remote devices", check "Reset innode table", check "convert windows drive letters", and check "utf-8 charset"
On Exports Tab, click on edit exports file. You need to setup like this:
Code:
my\path\towindows\folder -name:movies
my\path\to\someother\windows\folder -name:movies2
once you have entered all of your shares, save the file as exports.
now click restart server button on the right hand side.
you should see your mounts show up in the box.
Now download and install busyboxinstaller on your nook
type in mount script in busybox installer on the scripts tab by clicking the plus sign in the top right
name the script whatever you want
then in the command section type the following: You do not have to put the extra /sdcard/movies2 or so on if you are only mounting 1 folder
Code:
mkdir -p /sdcard/movies /sdcard/movies2 /sdcard/movies3 /sdcard/movies4
busybox mount -o nolock,tcp,hard,intr my.pc.ip.address:/myfoldermnt /sdcard/movies
the -p option on mkdir will check to see if the directory exists, if not it will create it
the mount command must be formatted exactly the same swapping out mypcipaddress for your local lan ip, and myfoldermnt for whatever you called your nfs share in your exports file, then mounting on the directory /sdcard/movies
once finished save the script and run it, then use root explorer to check and make sure /sdcard/movies exists and has your nfs content inside
you can set this script to run at boot also, if you are not at home no worries it will just error out and continue booting without you noticing
Setting up the Nook
Download Neon Codec
extract the neon folder to the root of either your internal or external sdcard
Download and install MX Player
Once installed configure it. Your movies may show up in the folder, dont attempt to play them yet.
click on settings and goto decoder
Make sure "Use h/w+ decoder" "h/w decoder local" "correct aspect ratio" are checked and nothing else
Now scroll to the bottom and you should see "custom codec" click it
navigate to the sdcard where neon folder is located. click on neon then click ok once the folder contents are displayed
MX Player is now setup, completely exit out of it
This next step is important because without it the h/w decoder buggers out and you are stuck with software decoder
navigate to main settings for tablet, enable developer options
scroll almost to the bottom and check "disable hw overlays"
now would be a good time to set your custom mount script in busybox installer to run at boot
now restart your nook
Open MX Player and you might not see your content, click the refresh symbol at top right and it should appear
select your movie of choice and go
enjoy full hd movies on your tablet!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Android gamers, today we will be learning how to play PC games on Android with the App DosBox Turbo; the best and fastest Dos Emulator for Android
Quick Links:
DosBox Turbo Performance Page
DosBox Turbo main information page
How to Play Dos Games on Android with DosBox Turbo
[Guide+Video] How to Play Fallout 1 with Dosbox Turbo
[Guide+Video] How to run Fallout 1 & 2 on Android with QEMU
[Guide+Video] How to Play Classic PC Games on Android with Exagear RPG (Paid app, Easier setup, Runs faster)
Dosbox Turbo Videos
How To Play PC Games on Android With DosBox Turbo
How to Play Fallout Tactics on Android with DosBox Turbo
System Requirements
Recommended:
CPU: Quad-Core/Octa-Core device 1.6Ghz
RAM: 2GB-3GB
Storage: 16GB
Minimum:
CPU: Dual-core 1.5Ghz
RAM: 1GB (My default setup uses 256MB)
Storage: 8GB
Emulated PC Gaming System
CPU: Pentium 1 Processor @ 60-90Mhz (Performance will vary)
GPU: 2D=S3 Trio64V+ 4MB 3D=3Dfx Voodoo 1 8MB
RAM: 256MB(Default)
Audio: Sound Blaster 16
HDD: HDD image files mounted from your devices internal(default) or external storage. Full install around 2.5GB
-Dosbox Turbo System DxDiag on my Note 2
DosBox Turbo Tested Win9x Game List:
Age of Empires 1 & 2
Alpha Centauri
Anno 1602
Arcanum
C&C Red Alert 95
Civilization II
Combat mission Beyond Overlord
Commandos: Behind Enemy Lines
Command and Conquer Tiberian Sun
Diablo 1
Diablo 2
Dungeon Keeper
Dungeon Keeper 2 (Needs pentium_mmx CPU setting in Dosbox Config)
Dune 2000
Fallout 1
Fallout2
Fallout2: Restoration project
Fallout Tactics
Half life
Heroes of Might and Magic III
Homeworld 1
Homeworld cataclysm
Ignition
Interstate 76
Jedi Knight dark forces 2
Lionheart
Lords of the Realms 2
M.U.G.E.N
Neighbors from Hell
Nox
Populous The Beginning
Quake 1
Seven Kingdoms 2
Simcity 2000
Simcity 3000
Starcraft 1
Strategic command
The Journeyman Project
The Longest Journey
The Sims
Total Annihilation
Europa Universalis 2
Warhammer 40k
Z
DosBox Turbo Win9x Installation Guide:
1)a]First you will need to install the DosBox Turbo app (free or paid) on your Android device.
DosBox Turbo Play Store here (Paid but Faster)
Or
aFreeBox Play Store here (Free but Slower)
-Run the DosBox Turbo app and open the settings menu from either the pull-down menu at the Top(3 dots) or swipe the left side of the screen to reveal a menu.
-Go to DosBox Settings/Advanced DosBox Config check “3DFX Glide Support” and “Manual Mode”.
-You must restart the app before these changes will take effect.
b]Important Change Not in the Video:
-Dosbox Turbos default directory path to the dosbox.conf file changed sometime after I made the video.
-Due to these changes, you will need to modify the directory path back to the old default.
-Do this by selecting "Config Location" right under where you clicked “3DFX Glide Support” and “Manual Mode” in the previous step.
-Full location @ settings/Advanced DosBox Config/Config Location
-Modify the "Config Location" path by removing the red text between /dosbox.conf and the /<path to storage>/
-View the below examples and modify the path to your own dosbox.conf
Default dosbox.conf location modification example:
Before:
/<path to storage>/android/data/com.fishstix.dosbox/files/dosbox.conf
After:
/<path to storage>/dosbox.conf
How it looked on my Note 2:
Before:
/storage/emulated/0/android/data/com.fishstix.dosbox/files/dosbox.conf
After:
/storage/emulated/0/dosbox.conf
Download DosBox Turbo Win9x Gaming Packages:
2)a]Download version 1.0 here DirectX9.0C, 3dfx, SB16, Runs the most games
Or
2)b]Download version 2.0 here DirectX9.0C, 3dfx, SB16, CD/ISO support with Daemon tools 3.47
Note:Win9x, CD/ISO support with daemon tools makes emulation less stable.
Or
2)c]Download version 3.0 here DirectX8.0, 3dfx, SB16, runs slightly faster doesn't support as many games.
3)Free software to access our HDD img files:
-We will need software to access or HDD img files and transfer over game folders
-On PC install the free 30 day trial of WinImage and run the application.
-This program will allow you to open and save your game data to your empty hdd .img files.
Download WinImage 10.0 here or here
Or
On Android install the free Zarchiver app here to access your image files and zips.
4) Locate and extract HHD .img images files for game storage:
Open the Win9x package you downloaded and look for the hdd folder. Inside you will find the empty hdd images files to store your games and ISO’s. Extract the default hdd-2gb image file and open the folder.
(Optional) How to use different sized HDD image files:
-To change the size of the image file used you must modify the name and drive geometry in the dosbox.conf file
-You can edit the config file from your the DosBox Turbo app @ settings/Advanced DosBox Config/ Edit Config File/
Default hdd line in the dosbox.conf file:
imgmount d: /sdcard/hdd-2gb.img -t hdd -fs fat -size 512,63,64,1023
Change the hdd name and drive geometry in the dosbox.conf file:
-In the below example we are changing the data to accomidate a 1GB HDD image:
imgmount d: /sdcard/hdd-1gb.img -t hdd -fs fat -size 512,63,64,520
Driver Geometry:
2GB image: 512,63,64,1023
1GB image: 512,63,64,520
512MB image: 512,63,32,520
256MB image: 512,63,16,520
(Optional)How to use SDcard storage:
Warning! This doesn't always work properly with newer devices or versions of Android.
-Using the device's default internal storage is recommended and it might be required for the app to load .img files from your device.
-To store the image files onto an external SDcard you will need to open the dosbox.conf file and change the storage directory path.
-The directory path will vary across android devices. I'd recommend using a file explorer program to help find the correct path to your SDcard.
-Below are several common paths to external SDcards on various devices. Review the following information and change devices SDcard path accordingly in the dosbox.conf file.
Note: Some devices may have issues starting emulation using an external SDcard.
-If you experience any issues launching emulation or running games use the default internal memory.
Default internal storage path in the dosbox.conf file:
imgmount c: /sdcard/c.img -t hdd -fs fat -size 512,63,16,520
imgmount d: /sdcard/hdd-2gb.img -t hdd -fs fat -size 512,63,64,1023
Change the storage path to your external SDcard:
imgmount c: /sdcard1/c.img -t hdd -fs fat -size 512,63,16,520
imgmount d: /sdcard1/hdd-2gb.img -t hdd -fs fat -size 512,63,64,1023
or
imgmount c: /mnt/sdcard1/c.img -t hdd -fs fat -size 512,63,16,520
imgmount d: /mnt/sdcard1/hdd-2gb.img -t hdd -fs fat -size 512,63,64,1023
or
imgmount c: /mnt/extsdcard/c.img -t hdd -fs fat -size 512,63,16,520
imgmount d: /mnt/extsdcard/hdd-2gb.img -t hdd -fs fat -size 512,63,64,1023
or
imgmount c: /storage/extSdCard/c.img -t hdd -fs fat -size 512,63,16,520
imgmount d: /storage/extSdCard/hdd-2gb.img -t hdd -fs fat -size 512,63,64,1023
5) Open the image files:
On PC Now that WinImage is installed you can open the empty hdd.img’s by double-clicking them
-You can drag game folders directly into the open WinImage program
or
-You can also direct the program to the game folders from the WinImage menu @ image/inject a folder
Or
On Android Open the ZArchiver app locate a game folder and copy it
-Next direct the app to the HDD.img files and paste it directly into the empty image
6) Place Games folders into the .img files:
-Locate your fully installed games such as DRM free GOG games from GOG here, ISO images, or extracted game data.
-Playing Fallout on android requires some additional modding
-Review my guide below for "How to setup Fallout 1, 2, Tactics with DosBox Turbo:"
-Once your games are setup drag the folder(s) containing this data into the open hdd image files
-Save your new hdd.img and close the program
(Optional)Download the Free Official Fallout 1 Shareware Demo:
-If you don't have games available download the Fallout 1 demo here
-Just extract the zip files and run the Falldemo.exe from android or PC
7) Transfer Files to the Root directory of your internal storage:
On PC Connect your Android device to your PC with the USB cable and open your devices internal memory. Copy over the dosbox.conf, c.img, and hdd-2gb.img, files into this space; note that none of these files should be located in a folder.
Or
On Android use a file explorer app here or here to locate and place the files into the root directory of your internal storage.
8) Launch DosBox Turbo:
-Now you' are ready to start the DosBox Turbo app and play your PC games on Android, have fun!
Click here to watch me launch games with Dosbox Turbo.
Get the Hackers Keyboard with useful Arrow<^> keys:
Get the free Hackers Keyboard here from the Play Store
-It has a better layout for playing games and includes directional keys
-Click for large pic
How to play Games Fullscreen (No Black Bars):
-To play games fullscreen you'll need to disable the default Aspect Ratio setting
-This will stretch images to fill your display and remove the black bars from the sides of the screen
-Go to DosBox Settings/Keep Aspect Ratio remove the checkmark
How to use Virtual On Screen Buttons:
DosBox Turbo has 4 programmable virtual buttons that can be used for additional in-game controls.
-Click to see the pic.
-In the DosBox settings menu check “Overlay Buttons”.
-Open “Button/Controller Maps” and choose “Add button Mapping”.
-A new label will appear, click it “Map custom Button (x)”
-At the top select 1 of 4 custom buttons to map
-Now select “Dos key mapping” and assign a key to the button.
-Once done select ok and repeat this for all 4 buttons.
-A good setup for playing fallout would be:
-Btn A=space, Btn B=b, Btn C=I, Btn D=s
-space=end turn, b=change hands, i=inventory, s=skill index,
-There is a Fast Forward button at the very bottom of the “Dos key mapping” menu, scroll down all the way.
-Map this key and you can hold it down to increase the cycles.
-This helps to speed up long load times, but note it will distort any audio that is playing.
How to Improve DosBox Turbos Performance:
Increasing the default memory size:
Warning! Test your device with the default settings before attempting to increase the video or system memory sizes. With newer versions of Android, this can cause the app to crash at launch or display an "Insufficient memory" or "Low memory" error message.
Video Memory:
-Increasing the default video memory size can have a big impact on performance and frame rates
-Moar video memory can make more demanding games playable like Diablo 2, Fallout 2 RP, Quake 1, Half-Life...
-Changing the video memory size from 4MB to 32MB doubles the performance of the WinQuake 1 Benchmark
-Click for a large pic of Quake 1 benchmark results
-Open the "dosbox.conf" file and change the vmemsize= entry, once modified save the changes
-You can edit the config file from your the DosBox Turbo app @ settings/Advanced DosBox Config/ Edit Config File/
Before:
[dosbox]
vmemsize=4
After:
[dosbox]
vmemsize=32
System Memory:
-You can also increase the system memory size but this tends to make the app crash at launch
-Test the video memory change first before attempting to modify the system memory
-If your android device has 2GB+ of memory or more, then you can increase the usable memory from the default of 256MB to 512MB
-Open the "dosbox.conf" file and change the memsize= entry, once modified save the changes
-You can edit the config file from your the DosBox Turbo app @ settings/Advanced DosBox Config/ Edit Config File/
Before:
[dosbox]
memsize=256
After:
[dosbox]
memsize=512
Extra HDD space for Virtual Memory:
-Using a 1/2GB HDD and then allocating free space for virtual memory, could help to improve performance.
-Once you're running win9x right click on the vault 13 desktop icon and choose properties, select the performance tab,“virtual memory” at the bottom, click “Let me specify my own virtual memory settings”. Select the HDD and specify the amount of space you want to use for virtual memory.
-It will prompt you to reboot once you exit. Don’t reboot, choose no, and then shut down and re-launch the emulator.
-This will help to keep System Resources between 98-99% free, this helps to optimize the performance.
-You can check the performance by right-clicking on the Vault 13 desktop icon and selecting properties. Navigate to the performance tab at the top and look for “System Resources:98%free”.
DosBox Turbo Quick Menu:
-You can access the quick menu by swiping the left side of the screen.
- This will give you access to quick settings and toggles for your input devices.
-To improve load times you can select “Cycles” and increase this number.
-By default, it will be on Auto, which gives the best balance between sound quality and performance.
-Increasing this will cause the games to load faster but can badly distort the sound.
-You can Toggle this up in games that have long load times.
- Set the Cycles back to Auto once your game has loaded.
-You can also disable the sound in the DOSBox settings and play with increased cycles.
-This will significantly improve performance on slower devices.
How to setup Fallout 1, 2, Tactics with DosBox Turbo:
Fallout 2 Regular
-To play Fallout 2 on Android install Killap’s unofficial Fallout 2 patch.
1) Download and Extract the Unofficial patch here then open the folder.
2) Open the extracted patch folder, copy the "data" folder and paste it into your Fallout 2 install directory. (yes to overwrite the files)
3) Open the "Windows 95-98-ME" folder and copy and paste these files into your Fallout 2 install directory. (yes to overwrite the files)
4) Open the “Batch_work’ folder and copy and paste these files into your Fallout 2 install directory. Run the "master_dat_fix_up.exe" file (A window will pop up, wait for it..)
5) Next this is EXTREMELY important, in your Fallout 2 install directory delete a file called "patch000.dat"
6)Download and extract the Fallout 2 custom configs files .zip here
-Locate the fallout 2 config folder, here you will find two different Fallout 2 configs to choose from.
-Copy and paste the "fallout2.cfg" config file from "Config With video & music sounds" into your Fallout 2 folder.
-The music and ambient sounds in the game can be distorted and cause lag, turn them off if necessary.
Note: You can always turn off the music and video sounds from the games preferences menu.
-Config With video & music sounds: fixes sound data path, increases the max volume.
-Config Without video & music sounds: disables music and boosts performance, fixes sound data path, increases the max volume.
(Optional) Download and extract Mash’s Hi-Res patch here
Note This Hi-Res patch allows you to increase the resolution but it will impact game performance.
Fallout 2 Restoration Project
Note) The Fallout 2 Restoration Project has longer load times it requires a faster device than the regular version
-To play Killaps Fallout 2 Restoration Project on Android do the following.
1) Download and Extract the manual Restoration patch here open the folder.
2) Open the "main" folder and copy and paste these files into your Fallout 2 install directory. (yes to overwrite the files)
3) Open the "Windows 95-98-ME" folder and copy and paste these files into your Fallout 2 install directory. (yes to overwrite the files)
4) Open the “Batch_work’ folder and copy and paste these files into your Fallout 2 install directory. Run the "f2.bat" file (A window will pop up, wait for it..)
5) Next this is EXTREMELY important, in your Fallout 2 install directory delete a file called "patch000.dat"
6)Download and extract the Fallout 2 custom configs files .zip here
-Locate the fallout 2 config folder, here you will find two different Fallout 2 configs to choose from.
-Copy and paste the "fallout2.cfg" config file from "Config With video & music sounds" into your Fallout 2 folder.
-The music and ambient sounds in the game can be distorted and cause lag, turn them off if necessary.
Note: You can always turn off the music and video sounds from the games preferences menu.
-Config With video & music sounds: fixes sound data path, increases the max volume.
-Config Without video & music sounds: disables music and boosts performance, fixes sound data path, increases the max volume.
Fallout Tactics
-In order to make Fallout Tactics playable with DosBox Turbo, you will need to remove ambient sounds from the game.
-The result is faster smoother scrolling and less lagged gameplay by reducing CPU/disk usage.
-Optionally you can also remove the videos since they don’t run properly and take up extra space.
How to remove ambient Sounds and Optimize files:
-Use Odin’s Booster utility to modify the audio files so ambient sounds can be deleted.
-Download Odin's Booster Utility here
-Extract the Booster.exe into your Fallout Tactics game folder.
-Run the Booster.exe with admin privileges by right-clicking the exe
-Select "Browse" and direct the booster utility to your Fallout Tactics game folder (Example= C:\GOG Games\Fallout Tactics\)
-Next select sound_o.bos and sound_amb.bos under "Files to optimize". Click on "Optimize!"
-Now the ambient sounds folder will appear in your Fallout Tactics game folder @ \Fallout Tactics\core\sounds\ambient\
-Delete or remove the ambient sounds folder from the Fallout tactics game folder
-(Optional) Delete or remove the intro movie from fallout @ \Fallout Tactics\core\movies\intro.bik
Fallout 1 Dos Guide + Video
-The Fallout 1 guide is in the 2nd post, click here or scroll down
How to use Version 2.0 with CD/ISO support:
1)Start the Daemon tools program by click the desktop icon.
2)Tap the Icon that will appear in the bottom right corner.
-Select “Device 0: [E:] No media”
3)Find your ISO image and select it
-Autoplay should now start your CD.
Note:To use ISO files they must be located within a folder before transferring them to the HDD.img.
-If the ISO is not located in a folder it will attempt to fill the HDD image and won't work correctly.
-Click to see the pic.
Use this to Play Games like Star Wars Jedi Knight: Dark Forces II. This video demonstrates how to mount the ISO images using Daemon tools @1:28.
Troubleshooting:
General Issues:
-3Dfx glide support is not working properly in the current build 2.1.21 and could cause the app to crash when launching 3Dfx enabled games. It works properly in previous builds.
aFreeBox: Can't open configs with manual mode enabled and the default directory location
'Error occurred when gettings files content: dosbox.conf"
-Changing the default conf to the old default fixes the issue.
-Win9x emulation can be unstable while exploring your emulated desktop. Opening multiple windows can cause crashing and lockups.
-By adding ISO/CD support windows becomes less stable and you should mount your ISO images right away.
-To maintain Win9x image stability I would recommend going to the start menu and shutting down windows after gaming but then exit the app.
I've Tried everything and DosBox Turbo won't run on my Device:
Magic DosBox Play Store (Free but limited)
Note: If DosBox Turbo doesn't work with your device try the Magic Dosbox Dos emulator
-Pros: smooth mouse support, frequent updates, great for Dos games
-Cons: No 3dfx support, Ram limit set to 64mb, few games launch due to limited Ram
How to setup Magic Dosbox for Win9x:
- Open the app click the +, make a new game, check Expert Commands, click the gear symbols, set "memsize=64", set "cputype=pentium", set "sbtype=sb16", add the following to the auto exe line at the bottom of the cfg file.
"[autoexe]
Ecco off
imgmount c: /sdcard/c.img -t hdd -fs fat -size 512,63,16,520
imgmount e: /sdcard/hdd-2gb.img -t hdd -fs fat -size 512,63,64,1023
boot -l c"
Insufficient memory/Low memory Error Message
-Increasing the default memory amount on newer versions of Android can sometimes cause a "Low memory" warning message.
-If you get a "Low memory" error message or your device crashes to the desktop when you run the app, you may need to reduce the amount of memory used. Try 128MB or 64MB.
- This message could also indicate that there is not enough free memory on your Android device. You may need to reboot or clear away background apps.
-If you still have problems launching windows or finding the D drive make sure you are using the default internal storage for your .img files.
Fallout 2 Notes:
-Fallout 2 runs best with a resolution of 640x480 and an 8bit color depth for best results. Using higher resolutions or 16-32bit colors can cause the game to become unplayable.
-Killaps Restoration project version 2.3.3 can cause screen scrolling issues with maps such as Temple of Trials.
-Using the older RP 2.1.2b version works best with DosboxTurbo. ExaGear RPG can run the latest RP 2.3.3.
Killaps Fallout 2 Restoration Project Main Page here
CD/ISO support issues:
-Overtime using the ISO support can cause the C img to stop working correctly. I would recommend making a backup of the image once you have a game installed.
- If this happens you can copy the backed up C image over to your device again. Your saved games will be located on the D HDD image and will be unaffected.
-The CD Rom support makes emulation less stable and can cause error messages when starting win9x with DosBox Turbo.
- If you experience errors simply exit and restart the app.
-There are alternatives to installing game data from the ISO.
-You can use the WinImage program to extract the ISO’s contents to a folder.
-This can be added to an HDD image and the setup exe run from inside of an emulated win9x environment.
-Many classic games can be run with game fixes, that will allow you to play without the CD.
GameBurnWorld No-CD Game Fixes
-You can add CD/ISO support by downloading Daemon tools 3.47 here and installing the setup exe from inside of an emulated win9x environment.
-Once running win9x with Daemon tools disable autostart and automount or the image may crash when launching win9x.
How to Play Fallout 1 on Android with Dosbox Turbo
How to Play Fallout 1 on Android with Dosbox Turbo:
How to Play Fallout 1 on Android with DosBox Turbo(Video)
System Requirements
Recommended:
CPU: Quad-Core/Octa-Core device 1.6Ghz
RAM: 2GB-3GB
Storage: 16GB
Minimum:
CPU: Dual-core 1.5Ghz
RAM: 1GB (My default setup uses 256MB)
Storage: 8GB
How to play Fallout 1 on Android:
1)a]You will need to have the DosBox Turbo app installed on your Android device. Run the DosBox Turbo app and open the settings menu from either the pull-down menu at the Top or left side swiping menu. Go to “DosBox Settings/Advanced DosBox Config” check “3DFX Glide Support” and “Manual Mode”. You must restart the app before these changes will take effect.
DosBox Turbo Play Store (Paid)
Or
aFreeBox Play Store(Free but Slower)
Or
Magic DosBox Play Store (Free but no Turbo)
b]Important Change Not in the Video:
-Dosbox Turbos default directory path to the dosbox.conf file changed sometime after I made the video.
-Due to these changes, you will need to modify the directory path back to the old default.
-Do this by selecting "Config Location" right under where you clicked “3DFX Glide Support” and “Manual Mode” in the previous step.
-Full location @ settings/Advanced DosBox Config/Config Location
-Modify the "Config Location" path by removing the red text between /dosbox.conf and the /<path to storage>/
-View the below examples and modify the path to your own dosbox.conf
Default dosbox.conf location modification example:
Before:
/<path to storage>/android/data/com.fishstix.dosbox/files/dosbox.conf
After:
/<path to storage>/dosbox.conf
How it looked on my Note 2:
Before:
/storage/emulated/0/android/data/com.fishstix.dosbox/files/dosbox.conf
After:
/storage/emulated/0/dosbox.conf
2)You will need to have a copy of Fallout 1 the game, I got mine from GOG here. GOG makes the best version available but you can also use older CD/DVD copy of the game.
-Locate your copy of the Fallout 1
Fallout 1 directory Locations:
By default the GOG version of the game should be located at C:\GOG Games\Fallout
By default the CD or DVD version of the game should be located at C:\Program Files\BlackIsle\Fallout
3)DOS is no longer included with newer versions of Fallout 1(GOG). You will need to add support for it by doing the following:
-Download the Fallout 1 Official v1.1 DOS Patch here
-Extract the DOS patch files directly into your Fallout 1 game folder
-Download and extract the following DOS files into your Fallout 1 game folder, dos4gw.exe here, hmidet.386 and hmidrv.386 here
Or
-Get it as part of Fallout Fixt mod here
When selecting the type of install, there is an option to include the DOS exe
4)Download and extract the Fallout 1 configs files .zip here
-Locate the fallout 1 config folder, here you will find two different Fallout 1 configs to choose from. Copy and paste the "fallout.cfg" config file from the "Config With video & music sounds" into your Fallout 1 game folder.
-(Optional) If you have a slower device or experience sound/performance issues use the file from "Config Without Video & music sounds" instead. Copy and paste the "fallout.cfg" file into your Fallout 1 game folder.
-(Optional) Fallout 1 NPC Mod
-This patch allows you to edit your NPC follows weapons and inventory just like in Fallout 2
-Download and extract the "Data" folder here into your Fallout 1 game directory
5)Locate the "dosbox.conf" file also in the Fallout 1 configs package.
-This file will launch the game automatically with a modified auto exe line.
-Transfer both the "dosbox.conf" and the Fallout 1 game folder to your Android device.
-They will need to be located in your devices internal storage by default.
-Now you are ready to launch the DosBox Turbo app from your Android device and begin your adventure into the Wasteland.
Note: If you forgot to enable manual mode and then exit the app in step 1 the "dosbox.conf" will be overwritten and Fallout 1 won't load. If this happens recopy the "dosbox.conf" file to the device after redoing step 1.
Note: If you're installing this from android you may require a file manager program to move and extract the files, I recommend X-plore File Manager here
Get the Hackers Keyboard with useful Arrow <^> keys:
-Get the free Hackers Keyboard here
-It has a better layout for playing games and includes directional keys.
-Click to see the pic.
How to use Virtual On Screen Buttons:
-In the DosBox settings menu check “Overlay Buttons”.
-Open “Button/Controller Maps” and choose “Add button Mapping”.
-A new label will appear, click it “Map custom Button (x)”
-At the top select 1 of 4 custom buttons to map
-Now select “Dos key mapping” and assign a key to the button.
-Once done select ok and repeat this for all 4 buttons.
-A good setup for playing fallout would be:
-Btn A=space, Btn B=b, Btn C=I, Btn D=s
-space=end turn, b=change hands, i=inventory, s=skill index,
-There is a Fast Forward button at the very bottom of the “Dos key mapping” menu, scroll down all the way.
-Map this key and you can hold it down to increase the cycles.
-This helps to speed up long load times, but note it will distort any audio that is playing.
-Click to see the pic.
How to play Games Fullscreen (No Black Bars):
-To play games fullscreen you'll need to disable the default Aspect Ratio setting
-This will stretch images to fill your display and remove the black bars from the sides of the screen
-Go to DosBox Settings/Keep Aspect Ratio remove the checkmark
-Click for large pic
(Optional)Fallout Fixt Mod 0.81alpha July 5th 2015:
"Fallout Fixt exists to enhance, expand and improve upon the Fallout 1 experience. This includes fixing bugs, restoring features, modifying balance, adding new features, and many fixes to text/dialog. In addition to that, all other available mods and patches are rolled into Fixt (see below), meaning that Fallout Fixt is the only thing needed for "the best" Fallout 1 experience. As of the most recent version, this mod fixes roughly 150 bugs still present in the unofficial patches and adds roughly 170 features. In addition, there are hundreds if not thousands of text&dialog fixes."
-Fallout Fixt Mod NMA here
-Fallout Fixt Mod Moddb here
(Optional)How to use the new default paths for DosBox Turbo files:
What happened:
-The location for the "dosbox.conf" and the mounted storage changed after I made the video
-You can use the new default locations by reviewing the below info
Default DosBox Turbo configuration file:
/<path to storage>/Android/data/com.fishstix.dosbox/files/dosbox.conf
Note: Find your "dosbox.conf" in the above default location. You can replace it with the one included in my package
Default Dos game space that is mounted as C:
/<path to storage>/Download/
Note: Place your .img files or Dos games into the "download" folder in your devices internal storage
Default location for the manager app conf:
/<path to storage>/Android/data/com.fishstix.dosboxlauncher/files/dosbox/<game name>.conf
Note: A handy tool for making and storing multiple "dosbox.conf" files.
Troubleshooting Fallout 1
-If Dosbox turbo crashes at launch and you get the a message like
"Directory /storage/sdcard/ doesnt exist.
Drive C does not exist!"
or
"unable to change to: fallout.
Illegal command: fallout."
Then you will need to open up the dosbox.conf file and change the mounted storage path
Default dosbox.conf modification example:
Before:
mount c: /storage/<path to storage>/
c:
cd fallout
fallout
How it looked on my Note 2:
mount c: /storage/emulated/0/
c:
cd fallout
fallout
Other possible examples
mount c: /storage/sdcard0/
c:
cd fallout
fallout
mount c: /storage/sdcard1/
c:
cd fallout
fallout
mount c: /storage/sdcard/
c:
cd fallout
fallout
mount c: /storage/extSdCard/
c:
cd fallout
fallout
-If Fallout 1 launches but crashes from the main menu once you try to start or load a game, then, take a good look at the instructions and make sure you didn't miss anything in step 4. Step 4 requires you to add a fallout 1 custom config to the Fallout 1 folder. This corrects the path for the game data and could be the reason why you're unable to get past the start screen.
How to Play Dos Games on Android with DosBox Turbo
How to Play Dos Games on Android with DosBox Turbo
Original "Beginning DosBox Turbo for Newbies" main page click here
More help and device specific questions can be found in the FAQ here
Download Free DOS Shareware games here
This guide will teach you how to play the popular Dos game DOOM on Android:
Step 1) Install DosBox Turbo or aFreeBox onto your Android device:
DosBox Turbo Play Store (Paid)
Or
aFreeBox Play Store(Free but Slower)
Or
Magic DosBox Play Store (Free)
Step 2) Download Dos Games:
-In this example, we will be using the free DOOM Shareware package
-Click here to download the "doom19s.zip" shareware to your computer or Android device
-Most DOS games arrive in a zip archive, some need to be unpacked with a .bat file into a seperate folder
-Once you've completed this guide Download the DOS Freeware/Shareware game of your choice here
Step 3) Unzip your Game folder:
-On PC unzip the archive using a program like WinRAR or WinZip
-The "doom19s.zip" will unzip to a folder on your PC called "doom19s"
Or
-On Android use the ZArchiver app here to unzip the Dos games directly into the "Download" folder.
Step 4) Copy the game folder to your Android Device:
On PC-Plug your Android device into your computer via USB cable and locate the "Download" folder in the root directory of your internal storage.
-Copy the "doom19s" folder and other games into the "Download" folder
-On Android- The files should already be in the "Download" folder
(Optional)Create a new folder called "dos" where you can put all our DOS games to keep them organized
-This is very helpful but do it once you're familiar with navigating DOS
Step 5) Setup the GamePad app or a Game Controller:
-If you don't have a controller install and Enable the free GamePad application on your Android Device to get cursor controls here
-Once installed click the GamePad icon and follow the steps to enable it on your Android device
-Then follow the video for instructions on how to mapping the keys to play doom
Note: The instructions for mapping buttons on the gamepad are the same as mapping an actual controller (Xbox360, Nvidia Shield, Xperia Play). Follow this video to setup the controls for playing doom on Android
Step 6) Start DosBox Turbo and configure the game settings:
-Start the DosBox Turbo app and when you see the dos prompt (c: \)
-Now you will need to bring up the Keyboard and begin typing
How to bring up the keyboard:
In Portrait Orientation: At the top of the screen, you'll see a keyboard icon, click this to show/hide the keyboard.
In Landscape Orientation: There will be no icon bar at the top of the screen. You can swipe down (from top to bottom) to bring up the icon bar with the Keyboard icon. Swipe Up to hide it again.
In ANY orientation: You always have the option of swiping (from LEFT to RIGHT) across your screen to bring up the "Quick Menu". From the Quick Menu you can enable/disable the keyboard.
Finally, after you brought up the keyboard we're ready to input dos commands
Many games will need to be unpacked before launching
Type the following to unpack the files for doom
c:\> cd doom19s
c:\doom19s> install
-You will be asked "which drive to install to? (example:C)" press c
-It will ask "Enter directory name to copy into:" by default its "DOOMS" press enter to confirm
-Next "That directory does not exist! Create it?" press y
-You'll be asked about the setup keep pressing enter till the game launches.
-A new folder will be created called "DOOMS" @ c:\DOOMS and the game's data will be extracted there
DOOM should now launch. If you are using the free GamePad keyboard, switch from the keyboard to the gamepad by swiping from left to right across the keyboard itself. You can also run the setup.exe if you want to change the DOOM settings. The procedure is basically the same for most Dos games.
The next time you launch doom you will need to direct Dos to the newly created "DOOMS" folder:
c:\> cd dooms
c:\DOOMS> doom
To run the doom setup again do the following:
c:\> cd dooms
c:\DOOMS> setup
How to Launch other Dos Games:
-To launch other games replace the doom folder and exe names with ones from your desired game.
c:\> cd "game folder name here"
c:"game folder name here"> "game .exe or .bat name here"
Basic Dos Commands you will need full list here and here and here:
cd "your folder here" = change directory to the specified location
cd.. = change directory back one folder in the file system
cd\ = Takes you back to the root directory (c: in this case)
dir = list all the files in the current directory
-If you don't know the name of the file to launch a game or unpack an archive type dir to list the files
-Any files listed that end in .exe or .bat are the ones to input, for example, install.bat, SETUP.exe DOOM.exe
How to Quick Launch Games with DosBox Manager:
-Click here for and a great guide for setting up games with Dosbox Manager app
-You can use the DosBox manager app here to create and store multiple dosbox.conf files like the one I've posted below.
-These can be used to quickly launch games
-You create a profile for each game that saves your settings and makes an auto exe for Dos commands
-Watch the instructional video
Auto exe Examples:
Fallout 1 Auto exe:
mount c: /storage/emulated/0/Download/
c:
cd fallout
fallout
DOOM Auto exe:
mount c: /storage/emulated/0/Download/
c:
cd dooms
doom
Get the Hackers Keyboard with useful Arrow<^> keys:
Get the free Hackers Keyboard here from the Play Store
-It has a better layout for playing games and includes directional keys.
-Click to see the pic.
How to use Virtual On Screen Buttons:
DosBox Turbo has 4 programmable virtual buttons that can be used for additional in-game controls.
-Click to see the pic.
-In the DosBox settings menu check “Overlay Buttons”.
-Open “Button/Controller Maps” and choose “Add button Mapping”.
-A new label will appear, click it “Map custom Button (x)”
-At the top select 1 of 4 custom buttons to map
-Now select “Dos key mapping” and assign a key to the button.
-Once done select ok and repeat this for all 4 buttons.
-A good setup for playing fallout would be:
-Btn A=space, Btn B=b, Btn C=I, Btn D=s
-space=end turn, b=change hands, i=inventory, s=skill index,
-There is a Fast Forward button at the very bottom of the “Dos key mapping” menu, scroll down all the way.
-Map this key and you can hold it down to increase the cycles.
-This helps to speed up long load times, but note it will distort any audio that is playing.
How to play Games Fullscreen (No Black Bars):
-To play games fullscreen you'll need to disable the default Aspect Ratio setting
-This will stretch images to fill your display and remove the black bars from the sides of the screen
-Go to DosBox Settings/Keep Aspect Ratio remove the checkmark
How to Enable MIDI support:
-Open the dosbox.conf files and make the following changes
[midi]
# Only enable MIDI if you have the necessary MT32 ROM files
mpu401=intelligent
mididevice=mt32
mt32.thread=on
mt32.verbose=off
How to Play Classis GOG.com Dos Games with 3Dfx Glide Support:
-You will need to have 3Dfx support enabled in DosBox Turbo app
-Open the settings menu from either the pull-down menu at the Top or left side swiping menu
-Go to “DosBox Settings/Advanced DosBox Config” check “3DFX Glide Support” restart the app before these changes will take effect
-For games to play Dos Games with 3Dfx glide support (Blood, Tomb Raider,ect) you will need to download and extract this glide2x.ovl file into your game folder here
How to Use DosBox Turbo with GOG.img files and ISO's in Dos Games:
-Download pre-made configs for Blood and Tombraider with auto exes to launch the games here
Mounting ISO and IMG files with Dosbox Turbo:
1) Run DosBox go to “DosBox Settings/Advanced DosBox Config” check “3DFX Glide Support” and “Manual Mode”. You must restart the app before these changes will take effect.
2)Some games have ISO or IMG files that must be mounted in order to play the games. GOG games have data image files called "game.gog", you will need to mount these in order to play your GOG games. I suggest you add a line to your DosBox Turbo config file. You can do this by opening up your dosbox.conf file and adding the following lines. Note you can also manually type these commands into Dosbox Turbo but you will need to repeat this each time before launching the game. In addition, you can use the free Dosbox manager to create a quick launch profile with the auto exe lines and ISO/IMG file commands.
imgmount d: /sdcard/[path_to_game]/game.gog -t iso
or
imgmount d: /sdcard/[path_to_game]/gamename.iso -t iso
In this example the game data is located on your Android device in a folder named "tomb".
imgmount d: /sdcard/tomb/game.gog -t iso
In this example the game data is located on your Android device in a folder named "blood".
imgmount d: /sdcard/blood/game.gog -t iso
How to play the Elder Scrolls II - Daggerfall on Android:
How to Benchmark Dosbox Turbo:
Dos Doom Shareware Benchmarking:
Download the Doom and Quake Shareware package for Dosbox Turbo here
The Doom 1 timedemo 3 is used as the main benchmark for Dosbox turbo. To keep the results accurate across devices users should use the Doom1 Shareware v1.9 in conjunction with a preset Dosbox config file. The config file will automatically run the test and display the results.
Doom time demo results will be displayed as gameticks and realticks. In order to calculate the average Frames per second (FPS) we will enter these results into this equation 35(gameticks/realticks). The gameticks will always be 2134 for the Doom Shareware V1.9. If you have a different number then you aren’t using this version and results will not be comparable. Compare your results with those on the Dosbox Turbo performance page here
1) You will need to have the DosBox Turbo app installed on your Android device. Run DosBox Turbo and open the settings menu from either the pull down menu at the Top or left side swiping menu. Go to “DosBox Settings/Advanced DosBox Config” check “Manual Mode”. You must restart the app before these changes will take effect.
2) Download the Doom v1.9 shareware and config with Auto exe. Copy this file and folder into the root directory of your internal storage space. This is the area that opens by default from your computer with the USB cable, all your Android data is located here. The folder should be called doom and have all the data contained within. You can manually run the test by launching Doom, bringing up the console by pressing (`)and typing “timedemo demo 3”.
3) Launch the Dosbox Turbo app from your device and Doom will start and run time demo 3. Once complete you will see your results that you can calculate your average FPS from. Round up your results to the nearest 0.1FPS.
-Click to see pic.
4)Compare your results with the chart on the DosBox Turbo Performance Page here
Multiplatform benchmarking with Quake 1 in Win9x and Dos:
You can benchmark the Quake 1 timedemo in both Dos and win9x. This will allow you compare performance between Dos, win9x and win9x with Glide 3Dfx support. Results will be displayed as average frames per second (FPS). Dosbox Auto exe configs can be used for Dos benchmarks and automated benchmark shortcuts are used with win9x.
1) You will need to have the DosBox Turbo app installed on your Android device. Run the DosBox Turbo app and open the settings menu from either the pull-down menu at the Top or left side swiping menu. Go to “DosBox Settings/Advanced DosBox Config” check “3DFX Glide Support” and “Manual Mode”. You must restart the app before these changes will take effect.
2) Download the Quake shareware demo and config files. Copy the Quake folder into your devices internal storage space. This is the area that opens by default from your computer with the USB cable, all your Android data is located here. The folder should be called quake and have all the data contained within.
3) To run the Quake 1 Dos benchmark, copy the Quake Dos config from the folder onto your device. Launch the Dosbox Turbo app from your device and Quake will start and run the time demo via the auto exe. Once complete you will see your results as an average FPS. If it doesn’t start you can manually run the test by launching Quake, bringing up the console by pressing(`) and typing “timedemo demo1”.
4) To run the Quake win9x benchmark copy the Quake win9x config from the folder onto your device. Place the Quake shareware demo folder into your HDD image, save it and transfer it to the device. This is the same procedure covered in the video for playing PC games with Dosbox Turbo. Launch the app to start win9x, open the shortcut to D and find the Quake folder. Inside this folder you will find several benchmark shortcuts for both regular quake and GL quake. Two Quake mods have been added to the folder to enable 3DfX glide support, Pro quake and Joe quake. Run one of these shortcuts to automatically start the benchmark and display results once complete. Note Pro Quake is the recommended benchmark for Quake in win9x. Joe Quake displays more of the screen and is, therefore, harder to run but is more enjoyable for playing the actual game demo. All comparable benchmark results should be done with either Pro Quake or Pro Quake GL. Note the shortcut links expect the game data to be located @ D:\quake.
Quake Benchmark Shortcut Legend:
-wqpro-Benchmark (Pro Quake Software Benchmark)
-glpro-Benchmark (Pro Quake GL Benchmark)
-joequake-Benchmark (Joe Quake Software Benchmark)
-joequake-gl-Benchmark (Joe Quake GL Benchmark)
-winquake-Benchmark (Default software Benchmark)
Nice stuff. Thank you very much. Will try it as soon as I have more free time.
Envoyé depuis mon cm_tenderloin en utilisant Tapatalk 4
Technical Difficulties
((Amended due to not being able to post links -- I had pictures and links :/ Sorry I cannot provide them being as I am new to the forums and only signed up to respond to this thread in particular))
:good: I've watched the video and read the guide all the way through.
What I have been trying to do is play a Windows 98 compatible game called Ahriman's Prophecy made by Amaranth Games. It's a free game you can download from their website, and the stats on it say "Windows 98/XP/Vista".
I also have tried another one of their games, which is pay to play ($20US), called Aveyond: Rhen's Quest which is made by the same people. Despite trying both version 1 and version 2 of the guides you posted, as I've tried for about 5 hours, which has kept me entertained, but alas it still will not work. I'm pretty persistent, but being able to play these on the Nextbook would make me incredibly happy.
I am running the Android application on a Nextbook. I have Dsbox Turbo purchased and installed.
Technical Specifications:
1.5GHz ARM Cortex A9 Dual-Core processor
1GB DDR3 of system memory and 8GB on-board storage memory
8.0" touchscreen, 1024 x 768 resolution
Built-in 802.11b/g/n WiFi
Click to expand...
Click to collapse
My Config File:
imgmount c: /sdcard/c.img -t hdd -fs fat -size 512,63,16,520
imgmount d: /mnt/sdcard/external_sdcard/hdd-1gb.img -t hdd -fs fat -size 512,63,64,520
boot -l c
Click to expand...
Click to collapse
I can access them, but when I run the application Aveyond: Rhen's Quest it crashes the whole system.
When I run Ahriman's Prophecy it gets to a white loading screen with the loading screen icon on the mouse. I can move the mouse about, but if I leave it running for 30 minutes it will go to a blue screen, require me to press a key, and then crash Dosbox Turbo all together.
I have also tried compressing Aveyond: Rhen's Quest into an ISO file and running it through Daemon tools, just to see if it would work, and that too hit a dead end.
BOTH programs run fine on a PC, so there's nothing wrong with the .exe files, but I have a feeling I made a mistake in the installation somewhere. Dsbox loads up fine, it's just running the .exe programs themselves that is an issue.
system requirements
Taisynn said:
((Amended due to not being able to post links -- I had pictures and links :/ Sorry I cannot provide them being as I am new to the forums and only signed up to respond to this thread in particular))
:good: I've watched the video and read the guide all the way through.
What I have been trying to do is play a Windows 98 compatible game called Ahriman's Prophecy made by Amaranth Games. It's a free game you can download from their website, and the stats on it say "Windows 98/XP/Vista".
I also have tried another one of their games, which is pay to play ($20US), called Aveyond: Rhen's Quest which is made by the same people. Despite trying both version 1 and version 2 of the guides you posted, as I've tried for about 5 hours, which has kept me entertained, but alas it still will not work. I'm pretty persistent, but being able to play these on the Nextbook would make me incredibly happy.
I am running the Android application on a Nextbook. I have Dsbox Turbo purchased and installed.
My Config File:
I can access them, but when I run the application Aveyond: Rhen's Quest it crashes the whole system.
When I run Ahriman's Prophecy it gets to a white loading screen with the loading screen icon on the mouse. I can move the mouse about, but if I leave it running for 30 minutes it will go to a blue screen, require me to press a key, and then crash Dosbox Turbo all together.
I have also tried compressing Aveyond: Rhen's Quest into an ISO file and running it through Daemon tools, just to see if it would work, and that too hit a dead end.
BOTH programs run fine on a PC, so there's nothing wrong with the .exe files, but I have a feeling I made a mistake in the installation somewhere. Dsbox loads up fine, it's just running the .exe programs themselves that is an issue.
Click to expand...
Click to collapse
Version 1 and 2 are the same but 2 has CD/ISO support. The minimum system requirement for Aveyond 1: Rhen's Adventure starts with a 600Mhz CPU. Equivalently my Note 2 has a 75-90Mhz CPU when running PC games with DosBox Turbo. Remember to look at the Emulated Android PC Performance chart in the guide and see where your device fits. The most limiting factor is our current level of hardware. Games that require a CPU above 300Mhz are generally unplayable with current hardware. If you happen to have a Tegra 4 device and set GPU acceleration, then you might be able to make it happen.
To be able to post pics and links here you need to get your post count up. Checkout some of my other fun gaming threads, you might find something interesting. Cheers
How to Play Quake 1,2,3 & RTCW on Android
How to Play Baldur's Gate and Planescape: Torment on Android with GemRB
[Boot Animation] Roland's HP TouchPad Custom Boot Videos
Thanks!
RolandDeschain79 said:
Version 1 and 2 are the same but 2 has CD/ISO support. The minimum system requirement for Aveyond 1: Rhen's Adventure starts with a 600Mhz CPU. Equivalently my Note 2 has a 75-90Mhz CPU when running PC games with DosBox Turbo. Remember to look at the Emulated Android PC Performance chart in the guide and see where your device fits. The most limiting factor is our current level of hardware. Games that require a CPU above 300Mhz are generally unplayable with current hardware. If you happen to have a Tegra 4 device and set GPU acceleration, then you might be able to make it happen.
To be able to post pics and links here you need to get your post count up. Checkout some of my other fun gaming threads, you might find something interesting. Cheers
Click to expand...
Click to collapse
Thank you very much for the response. I'm more interested in RPG games, so playing Fallout really is not necessarily my goal. I figured it could possibly have something to do with that. Still, I was entertained enough playing with the guide. It's really good, and I at least succeeded with getting DosBox Turbo working. \o/
Wanted to let everyone know the 2.1.5 release of DosBox Turbo supports CD-Audio (ie. mixed mode CD's), so mounting bin/cue files from GoG should now allow for cd-audio.
Great News, Great Update!
gene_wildhart said:
Wanted to let everyone know the 2.1.5 release of DosBox Turbo supports CD-Audio (ie. mixed mode CD's), so mounting bin/cue files from GoG should now allow for cd-audio.
Click to expand...
Click to collapse
Thats fantastic news! I can't wait to try it out:good: Gaming just isn't the same without the music
future of dosbox?
what level of games are possible ? for instance could you play warcraft 3? will we ever se that kind of emulation?
The future is friendly
Dasher1 said:
what level of games are possible ? for instance could you play warcraft 3? will we ever se that kind of emulation?
Click to expand...
Click to collapse
That all depends on the power of the Android device and the system requirements of the game. I have yet to try using this with a Tega 4 device but we can expect more GPU heavy Android devices from Nvidia in the future. If a game can be run with a Voodoo 1 and low powered CPU then it would be within the realm of possibility. Voodoo 3Dfx support is a new and experimental feature currently, so games will run better in software mode. We can expect this to improve as development continues but it might be a few years before something like WC3 is playable. Have a look at the current hardware info below. If a fast current device provides around 100mhz CPU then we need something 4x to 6x faster for WC3.
Emulated Android PC Performance
Recommended System Requirements:
CPU Quad- Core, Dual-core 1.2Ghz+, equivalent or better.
GPU Adreno 220+, Nvidia Tegra2/3/4, equivalent or better.
2GB, 1GB, 512MB. My Config asks for a min or 256MB & shouldn't be run on a device with less than 512MB.
8GB disk space
Minimum System Requirements:
1Ghz Single-Core CPU with 512MB of Ram
4GB Disk Space
Android to PC hardware conversion:
Quad Core Samsung Exynos (1.6 Ghz - Samsung Galaxy Note II) ~ Pentium 75 - 90
Quad Core Nvidia Tegra3 CPU (1.5Ghz) ~ Pentium 60-75Mhz
Dual Core Nvidia Tegra2 CPU (1Ghz) ~ [email protected]
Dual Core A9/Exynos Processor (Samsung Galaxy II @ 1.2Ghz) ~ [email protected]
Dual Core Qualcomm Snapdragon S3 (MSM8260 1.5Ghz) ~ [email protected]
Single Core Generic Cortex A8 (1Ghz) ~ [email protected]
DosBox Turbo main information page
DosBox Turbo Performance Page
RolandDeschain79 said:
That all depends on the power of the Android device and the system requirements of the game. I have yet to try using this with a Tega 4 device but we can expect more GPU heavy Android devices from Nvidia in the future. If a game can be run with a Voodoo 1 and low powered CPU then it would be within the realm of possibility. Voodoo 3Dfx support is a new and experimental feature currently, so games will run better in software mode. We can expect this to improve as development continues but it might be a few years before something like WC3 is playable. Have a look at the current hardware info below. If a fast current device provides around 100mhz CPU then we need something 4x to 6x faster for WC3.
Emulated Android PC Performance
Recommended System Requirements:
CPU Quad- Core, Dual-core 1.2Ghz+, equivalent or better.
GPU Adreno 220+, Nvidia Tegra2/3/4, equivalent or better.
2GB, 1GB, 512MB. My Config asks for a min or 256MB & shouldn't be run on a device with less than 512MB.
8GB disk space
Minimum System Requirements:
1Ghz Single-Core CPU with 512MB of Ram
4GB Disk Space
Android to PC hardware conversion:
Quad Core Samsung Exynos (1.6 Ghz - Samsung Galaxy Note II) ~ Pentium 75 - 90
Quad Core Nvidia Tegra3 CPU (1.5Ghz) ~ Pentium 60-75Mhz
Dual Core Nvidia Tegra2 CPU (1Ghz) ~ [email protected]
Dual Core A9/Exynos Processor (Samsung Galaxy II @ 1.2Ghz) ~ [email protected]
Dual Core Qualcomm Snapdragon S3 (MSM8260 1.5Ghz) ~ [email protected]
Single Core Generic Cortex A8 (1Ghz) ~ [email protected]
DosBox Turbo main information page
DosBox Turbo Performance Page
Click to expand...
Click to collapse
Thank you for this guide!
Here's a guide another user wrote for getting Wing Commander: Privateer (and its expansion Righteous Fire) to work with dosbox. http://forum.xda-developers.com/showpost.php?p=43336721&postcount=2
I have a question for you if you know. How can we disable quickmenu? Or at least get it to stop showing up when I move the cursor left, because even when I change the settings to be Button Only (and which button would that be btw?) it still pops up when I move my joystick on the MOGA to the left. Most of the time, when the menu pops up, DosBox crashes that's why I want to disable it.
Quick menu
Bojamijams said:
Thank you for this guide!
Here's a guide another user wrote for getting Wing Commander: Privateer (and its expansion Righteous Fire) to work with dosbox. http://forum.xda-developers.com/showpost.php?p=43336721&postcount=2
I have a question for you if you know. How can we disable quickmenu? Or at least get it to stop showing up when I move the cursor left, because even when I change the settings to be Button Only (and which button would that be btw?) it still pops up when I move my joystick on the MOGA to the left. Most of the time, when the menu pops up, DosBox crashes that's why I want to disable it.
Click to expand...
Click to collapse
You can get to the quick launch button by bringing up an additional menu along the top. Do this by swiping down on the screen, swipe up to hide it. In the upper left corner you can find the button to bring up the quick menu options. You can also set an overlay button to bring it up in the settings menu, that's covered in the guide. Changing the setting to "Button Only" should fix the problem but obviously somethings wrong if its crashing the app.
Install and run this free Alogcat app from the Play Store.Next start up DosBox Turbo and crash it a few times, open the alogcat app and go to settings(3 Dots), save it. Connect the device with the USB cable, open the storage and look for the alogcat folder. Copy the small text file and upload it here. Also let us know what kind of device you're using and the version of Android you're running. Now the developer can take a look at your alogcat and solve the problem.
Cheers
RolandDeschain79 said:
You can get to the quick launch button by bringing up an additional menu along the top. Do this by swiping down on the screen, swipe up to hide it. In the upper left corner you can find the button to bring up the quick menu options. You can also set an overlay button to bring it up in the settings menu, that's covered in the guide. Changing the setting to "Button Only" should fix the problem but obviously somethings wrong if its crashing the app.
Install and run this free Alogcat app from the Play Store.Next start up DosBox Turbo and crash it a few times, open the alogcat app and go to settings(3 Dots), save it. Connect the device with the USB cable, open the storage and look for the alogcat folder. Copy the small text file and upload it here. Also let us know what kind of device you're using and the version of Android you're running. Now the developer can take a look at your alogcat and solve the problem.
Cheers
Click to expand...
Click to collapse
I was hoping the 'Button Only' would indeed by the fix I need but the menu still pops up when I move my analog stick to the left for more then a second. Something has to be odd about that right?
RolandDeschain79 said:
You can get to the quick launch button by bringing up an additional menu along the top. Do this by swiping down on the screen, swipe up to hide it. In the upper left corner you can find the button to bring up the quick menu options. You can also set an overlay button to bring it up in the settings menu, that's covered in the guide. Changing the setting to "Button Only" should fix the problem but obviously somethings wrong if its crashing the app.
Install and run this free Alogcat app from the Play Store.Next start up DosBox Turbo and crash it a few times, open the alogcat app and go to settings(3 Dots), save it. Connect the device with the USB cable, open the storage and look for the alogcat folder. Copy the small text file and upload it here. Also let us know what kind of device you're using and the version of Android you're running. Now the developer can take a look at your alogcat and solve the problem.
Cheers
Click to expand...
Click to collapse
Just an update for others who might be having the same issue too (that being, the QuickMenu pops up when you move a Dpad/Analog stick left for more then a 1 second
The issue was that I mapped the physical Dpad on my Moga Pro to the left/right/up/down but used the analog stick to fly. You have to map the stick that you will use for movement (ie. will be held down a lot) to avoid this problem.
Not sure if this was it or the fact I've switched to CM10.2 but bringing up the QuickMenu (intentionally now) no longer crashes it. Also I was using IntelliDemand governor before but am now using Interactive. That may also have been it.
Anyway Privateer 1 with Moga Pro on my phone is amazing. So much nostalgia!!
noobies need help
ive already do all of that.. but how to boot..
c:imgmount d: /sdcard blablabla
c:boot -| c
then error
what you talkin bout willis
dzar84 said:
ive already do all of that.. but how to boot..
c:imgmount d: /sdcard blablabla
c:boot -| c
then error
Click to expand...
Click to collapse
You've already done what now?? Its all setup for you, you don't type anything..... Time to rewatch the video.
dzar84 said:
ive already do all of that.. but how to boot..
c:imgmount d: /sdcard blablabla
c:boot -| c
then error
Click to expand...
Click to collapse
I think your problem may be the last line. It needs to read:
boot -l c
---------- Post added at 08:59 PM ---------- Previous post was at 08:56 PM ----------
Bojamijams said:
Just an update for others who might be having the same issue too (that being, the QuickMenu pops up when you move a Dpad/Analog stick left for more then a 1 second
The issue was that I mapped the physical Dpad on my Moga Pro to the left/right/up/down but used the analog stick to fly. You have to map the stick that you will use for movement (ie. will be held down a lot) to avoid this problem.
Not sure if this was it or the fact I've switched to CM10.2 but bringing up the QuickMenu (intentionally now) no longer crashes it. Also I was using IntelliDemand governor before but am now using Interactive. That may also have been it.
Anyway Privateer 1 with Moga Pro on my phone is amazing. So much nostalgia!!
Click to expand...
Click to collapse
Just a note that any inputs that are not mapped in the DosBox Turbo button mapper will be ignored by DosBox itself and passed directly to the underlying Android OS. Depending on your ROM/OS, a left dpad or stick movement often defaults to something similar to the back button.
Glad you were able to resolve the issue by mapping the analog stick!
Joystick in WinX box?
Roland,
Have you been able to get the joystick working in your Win(x) machine? I have note 3, installed Falcon 4 and Xwing vs TIE, run like champs but need a joystick.
Thanks
Which joystick?
usmchummer said:
Roland,
Have you been able to get the joystick working in your Win(x) machine? I have note 3, installed Falcon 4 and Xwing vs TIE, run like champs but need a joystick.
Thanks
Click to expand...
Click to collapse
Can you be a little more specific about "the joystick" are you talking about a particular model or connection, OTG, Bluetooth?
Running Remix OS next to a Linux distro has it's advantages, first of all it's easy to update by just replacing the new system.sfs/img.
Next it's easy to manage backups from working configurations and it's easy to boot by using the Grub Bootloader.
The ideal configuration for me was a triple boot.
1- Windows
2- Linux Mint 17
3- Remix OS
Here are some quick steps getting you guys started once you have you'r linux distro up and running feedback is always welcome.
1: Create a separate EXT4 partition I suggest 16/32GB (use gparted or something)
2: Create a new folder /media/RemixOS and Mount the partition eg: sudo mount -o rw /dev/sdxx/media/RemixOS/
3: Go to the mounted drive /media/RemixOS inside that folder create one more folder "data".
4: Download Remix OS (for me this was Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip)
5: Extract the archieve (you should have the Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img) by now.
6: Mount this downloaded *img and copy initrd.img install.img kernel ramdisk.img to /media/RemixOS/
7: Copy system.sfs to desktop and run unsquashfs system.sfs in terminal (this will give you a new system.img).
8: You can now root this image or go to the next step, see (http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769) rooting.
9: Copy the system.img to /media/RemixOS
10: Okay now we need to edit the /etc/grub.d/40_custom
sudo gedit /etc/grub.d/40_custom
Example:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
set root=(hd2,gpt3) << Make sure to set the right root drive here
linux /kernel DATA=/data SRC=/ root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive
initrd /initrd.img
}
Reboot and enjoy Remix OS! ¨First boot might take a while!¨
11: Optional if you rooted but (recommended): you should change the build.prop in the /system partition.. why ?
For example my graphics driver only supports opengl 2.0, however by default RemixOS used 3.0 on build.prop
Some apps are looking for this settings and this results that some apps might not work at all, Example for me was Sim City BuildIt it just diden't start.
The plex app was not able to play my video collection at all.
All of this is fixed by changing this setting.
Go to settings > about > find the OpenGL version your driver uses and change the settings.
So if we should change the value ro.opengles.version
For OpenGL ES 2.0, set:
ro.opengles.version=131072
For OpenGL ES 1.1, set:
ro.opengles.version=65536
For OpenGL ES 1.0, set:
ro.opengles.version=65535
For OpenGL ES 3.0, set:
ro.opengles.version=196608
For Opengl ES 3.1, set:
ro.opengles.version=196609
This should prevent apps from detecting the wrong OpenGL version.
You can use ES File Manager or something to change the file.
If I use an external HDD and set up the grub will the external HDD have to be plugged in every time?
Orion116 said:
If I use an external HDD and set up the grub will the external HDD have to be plugged in every time?
Click to expand...
Click to collapse
Only every time your wanna use Remix OS
Sent from my HTC Explorer A310e using XDA Labs
MSF Jarvis said:
Only every time your wanna use Remix OS
Sent from my HTC Explorer A310e using XDA Labs
Click to expand...
Click to collapse
That would work, but one problem for the external device could be that a other device steals the default root drive mapping.
For example if you plugin a other usb device the string root= might need a change for RemixOS.
TerrorToetje said:
That would work, but one problem for the external device could be that a other device steals the default root drive mapping.
For example if you plugin a other usb device the string root= might need a change for RemixOS.
Click to expand...
Click to collapse
What do you mean?
Please write a complete example that insert into gksudo gedit /etc/grub.d/40_custom
Kyurem_BoG said:
Please write a complete example that insert into gksudo gedit /etc/grub.d/40_custom
Click to expand...
Click to collapse
Can you give me the output of "sudo blkid" ?
I'm almost there but I've never edited GRUB before.
When I run sudo blkid I get:
/dev/sda1: UUID="6cfde26d-ae1a-4d0a-ad3e-5272241147d4" TYPE="ext4" PARTUUID="0002aa97-01"
/dev/sda5: UUID="2275ddfe-0b4c-4f34-afaf-f494abe9627d" TYPE="ext4" PARTUUID="0002aa97-05"
/dev/sda6: UUID="ce804863-11a8-4b39-9684-160883c046da" TYPE="swap" PARTUUID="0002aa97-06"
/dev/sda7: UUID="4bb10e85-d2bd-4dbe-8ed9-398eeee0027e" TYPE="ext4" PARTUUID="0002aa97-07"
/dev/sda8: UUID="5ed57704-0ff1-46c1-a6dd-06791ad567ce" TYPE="ext4" PARTUUID="0002aa97-08"
And /dev/sda5 is my RemixOS partition. So how should my .../custom_40 look?
Thanks for this!
[
This should prevent apps from detecting the wrong OpenGL version.
You can use ES File Manager or something to change the file.[/QUOTE]
My build.prop was correct out of the box but I can't get Plex to play anything. Any ideas?
Does it also work with Remix OS Beta? Im using 64bit efi, but it is stuck at pulsating Remix OS logo. When I enter console (alt+f1), I can see all the files (via ls), data folder got filled with regular android-like folders (although "app" folder is empty). Also there doesn't seem to be any error in dmesg/logcat. Any advice?
My partition is 16GB EXT4, using Ubuntu 15.10 as primary OS.
azerty keyboard
Please make AZERTY keyboard compatible
Thanks
Oh yea, I've finally got it up and running. There was a problem with /data permissions/owner so I've deleted whole folder and it booted up just fine.
EDIT: Resetting on each boot.
sorry,can you explain me
sorry bro,i m a real noob.recently i installed linux mint,its inadequate.i want android ny side.can you explain me in detail:crying: