Related
I've tried everything, are people who use OSX left behind? I can't root and I want to! Is there a solution?
Well I can only speak from little experience with rooting but it seems that you either have to use Boot Camp to install Windows on a partition on your HDD or either using VMWare or some other VM program to install windows on your mac.
Either way it is sad that we have to install that POS Operating System.
I agree with you though.....we should not be left in the dark because we run a superior Operating System rather than Windows.
dwnload windows 7 ISO(100% legal as Microsoft has download links), create small partition and install windows 7. This will give u a 30 day trial. Root it, then delete the windows partition once you boot back into osx
Or try vmware player and see if you can send through the USB device
Btw wrong section, this is a general question
chatch15117 said:
dwnload windows 7 ISO(100% legal as Microsoft has download links), create small partition and install windows 7. This will give u a 30 day trial. Root it, then delete the windows partition once you boot back into osx
Or try vmware player and see if you can send through the USB device
Btw wrong section, this is a general question
Click to expand...
Click to collapse
LOL woops I thought this was general *is a space case* and I can't install win7 because as of the moment I can only use my mom's OSX computer. I'll just have to wait until I can fix my windows computer.
Digiguest said:
I agree with you though.....we should not be left in the dark because we run a superior Operating System rather than Windows.
Click to expand...
Click to collapse
LOL
OT: I'm a computer programmer by trade, and I recently had to port some code I originally programmed in Windows to OSX, and I can tell you that OSX is one of THE least intuitive interfaces I have ever worked with, and I have various flavors of Linux/Ubuntu running at home as well. It's like they are trying to be different just to be "not Windows." Resizing a window using ONLY one corner? WTF is that? Fast switching only between running programs and being f'ed if said program is running multiple windows and the window you want is behind another one who's "resizing corner" is off to the side? Again, WTF?
You basically have to be completely bought in to their dumbed down interface to be comfortable with it.
Anywho.
carrrnuttt said:
LOL
OT: I'm a computer programmer by trade, and I recently had to port some code I originally programmed in Windows to OSX, and I can tell you that OSX is one of THE least intuitive interfaces I have ever worked with, and I have various flavors of Linux/Ubuntu running at home as well. It's like they are trying to be different just to be "not Windows." Resizing a window using ONLY one corner? WTF is that? Fast switching only between running programs and being f'ed if said program is running multiple windows and the window you want is behind another one who's "resizing corner" is off to the side? Again, WTF?
You basically have to be completely bought in to their dumbed down interface to be comfortable with it.
Anywho.
Click to expand...
Click to collapse
+1
Yea, I'm gonna close this. Desktop OS flame war doesn't have anything to do with phones.
Hi,
I started experimenting with this idea. I have WP8 files extracted from a firmware file. I copied these files to my surface RT. I was able to run some WP8 applications out of the box. however, applications that require UIXmobile.dll (WP GUI) failed to run. Now both WP8 and W8 share the NT core. so some libraries would just work. now the main WP8 library UIXmobile.dll doesn't work out of the box. as it uses a different function to create the gui for its applications.
I was thinking of something similar to what has been done by "mamaich", to implement a library that will replace the WP8 call wtith the standard W8 call (for example: use createProcess instead of createApplication) and pass the common calls to the already implemented APIs.
sadly , It's a very difficult task for me to do. I'll be spending time on it but i can't promise of any fast results.
I'd like to thank the authors of these threads for their wonderful work:
1. Running x86 apps on WinRT devices (by mamaich)
http://forum.xda-developers.com/showthread.php?t=2095934
2. RT Jailbreak Tool (By netham45 )
http://forum.xda-developers.com/showthread.php?t=2092158
3. Desktop apps ported to Windows RT (by GoodDayToDie)
http://forum.xda-developers.com/showthread.php?t=2092348
4. (FFU) ImgMount Tool v.1.0.15 (by AnDim)
http://forum.xda-developers.com/showthread.php?t=2066903
Which apps worked without tinkering?
Oh, very cool idea. It would probably only work for actual WP8 apps at first (not WP7.x apps, as those would require either a Silverlight or XNA runtime), but the idea has merit for sure. It was speculated for a long time that running WP8 apps on Win8/Windows RT would be possible, as both are written against the WinRT API, but that never happened. If we can make it happen ourselves, though... that would be awesome.
Of course, ideally we'd want to be able to access the store, since there aren't a lot of WP8 app packages floating around where we could use them. That's probably a very tricky problem in and of itself, although you could try extracting the store EXE and seeing what is required to make it work...
I think windows phone(os) is just a min gui shell for windows rt.so its possible to run the shell in windows rt.and maybe a windows phone can run windows rt.
windowsrtc said:
I think windows phone(os) is just a min gui shell for windows rt.
Click to expand...
Click to collapse
Not exactly. It's the same shell (well, the next rev) that was running on top of wince for WP7.
Is it an alternate shell (like Explorer), or a totally separate graphics subsystem?
Boomchaos said:
Which apps worked without tinkering?
Click to expand...
Click to collapse
there is a program called telwp.exe that was able to reach a certain point. I attached a screen shot of 3 different apps. 2 apps showed something before crashing (telwp, nokia_security). and the third app crashed with an error message. other wp apps usually crash silently leaving an error message about a faulty CoreUi.dll in the evenlog .
I tried running it on Virtualbox but it didn't go well so here is Android 4.3 running on VMware Workstation.
Download 4.3 from http://android-x86.org
chronic8000 said:
I tried running it on Virtualbox but it didn't go well so here is Android 4.3 running on VMware Workstation.
Download 4.3 from http://android-x86.org
Click to expand...
Click to collapse
Was this just a clean install from the .iso into VMWare? I'm guessing android-x86-4.3-20130725.iso from http://www.android-x86.org/download
Yes with the modification at boot to make it 1080p. Need to work out the best DPI for it though.
Running on virtual box but not well.
Anyone knows how to rotate screen there? often the game rotates it and then it becomes unusable as mouse directions also reverse.
Candoris said:
Anyone knows how to rotate screen there? often the game rotates it and then it becomes unusable as mouse directions also reverse.
Click to expand...
Click to collapse
I know this might be a bit late but I found holding F9-F12 works to force a set rotation.
VirtualBox is working fine. But where i'm very interested is the USB pass-through. I wonder how it performs vs VBox one.
I also know VMware got a virtual USB sniffer. It could be awesome to emulate/create/debug/use custom USB devices.
In example, i'm using an USBAudio sound card. Due to the actual limitation of Android, i'm not able to adress it from SDK (sadly !) and i must do from NDK. VirtualBox fails miserably when i try to open my USBAudio class device (the VM is crashing).
Does you USB devices are working with VMWare ?
Got success installing android 4.6 on a VMware 9. The problem is Apps installing.
I can install apps (.apk) from the internet like SnapPea but not from my computer (no explore) although I modified Android.vmx
Code:
ethernet0.virtualDev = "e1000" to "vlance"
Any idea?
Salutations folks,
Before you get ready to get your flame on, I'm NOT asking about the STATUS of a RT Windows 8.1 Jailbreak. I'm posting about jailbreaks in general. I'm from a linux/android background. I got an Asus Vivotab RT LTE (AT&T version) for a steal off 1Sale. Before I even looked into doing anything with my tablet, I updated it to 8.1. Then I finally got around to looking into running desktop apps on Windows RT (not knowing how it all worked with RT vs desktop), I ran into the issue of not being able to run them (duh, right?). Then I found out about jailbreaking. So.. do you HAVE to jailbreak to run desktop apps? As I understand it, we currently have to run 8.0 to jailbreak/run desktop apps, yes? Well.. I obtained the Asus recovery files to downgrade my 8.1 to 8.0. On a whim, I updated my 8.1 with the 8.1 big spring update (basicly 8.1.1). I seem to be able to run some of the ported desktop apps without any problem. Am I missing something? How'd my tablet manage that without having run the jailbreak? And jailbreak doesn't work on 8.1 anyways? Before anyone says I'm full of it.. (you can click the thumbnail for full pic)
(windows rt 8.1 with 8.1 spring update installed)
(windows rt 8.1 running desktop 7zip)
(windows rt 8.1 running desktop putty)
(windows rt 8.1 running desktop notepad++)
Can anyone clarify if I'm missing something or I've come across an anomaly or even a blessed relief?
Thanks.
This is sure amazing
1. Can you run *any* unsigned application or only a few work (and the rest throw signature errors?)
2. Check the status of Secure Boot in PowerShell. Run as admin, "Get-SecureBootPolicy", press enter (http://technet.microsoft.com/en-us/library/jj603043.aspx)
3. Could you detail exactly your process? I understand that you did the following:
(On 8.1) Run unsigned desktop app, fail with digital signature error.
(Downgrade) Downgrade to 8.0 -> (On 8.0) Run Jailbreak -> Run Desktop Apps and they work.
(Upgrade) Upgrade to Windows RT 8.1 (via Store?) -> Upgrade to 8.1.1 (Spring Update) via Windows Update -> Run Desktop Apps and they work (partly or all of them?)
4. I'm not sure if it'd be any useful, but perhaps you could look in your EFI system partition (mountvol S: /s) as there has been a previous report of Asus leaving debug tools in VivoTab RTs before (http://forum.xda-developers.com/showthread.php?t=2477285). If you could retrieve a "debug" version of Secure Boot Policy from your EFI partition then it means that Secure Boot has just disabled itself on your tablet. It's highly unlikely, however, since you weren't able to run desktop apps in your original 8.1 install...
jimmielin said:
This is sure amazing
1. Can you run *any* unsigned application or only a few work (and the rest throw signature errors?)
Click to expand...
Click to collapse
I only grabbed the ported Putty, 7zip and Notepad++ desktop apps as those were the only ones that I was needing.. Oh I recently grabbed the FileZilla one too. All ran without any problems and never got any signature errors. Hell.. even my 7zip integrated into the shell and replaced archive icons with 7zip archive icons and opens my archives by default with the desktop app. Were there any particular applications you wanted me to try so that I can see if I can replicate any signature errors?
jimmielin said:
Check the status of Secure Boot in PowerShell. Run as admin, "Get-SecureBootPolicy", press enter (http://technet.microsoft.com/en-us/library/jj603043.aspx)
Click to expand...
Click to collapse
SecureBoot is enabled and it displays a Publisher GUID. Confirm-SecureBootUEFI confirms SecureBoot is enabled too.
jimmielin said:
3. Could you detail exactly your process? I understand that you did the following:
(On 8.1) Run unsigned desktop app, fail with digital signature error.
(Downgrade) Downgrade to 8.0 -> (On 8.0) Run Jailbreak -> Run Desktop Apps and they work.
(Upgrade) Upgrade to Windows RT 8.1 (via Store?) -> Upgrade to 8.1.1 (Spring Update) via Windows Update -> Run Desktop Apps and they work (partly or all of them?)
Click to expand...
Click to collapse
hmm
- Received clean OEM install Vivotab RT LTE with RT 8.0
- Upgrade to Windows RT 8.1 via Store
- (attempted to run some ported desktop apps, received error)
- was going to downgrade back to 8.0 after getting Asus recovery files but instead..
- Upgrade to RT 8.1.1 (Spring Update) via Windows Update
- (attempted to run some ported desktop apps, ran successfully, no errors)
NOTE: Not once had I ever gotten around to downloading or installing the Jailbreak. Is there some way to confirm if I have the jailbreak installed at startup or something?
jimmielin said:
4. I'm not sure if it'd be any useful, but perhaps you could look in your EFI system partition (mountvol S: /s) as there has been a previous report of Asus leaving debug tools in VivoTab RTs before (http://forum.xda-developers.com/showthread.php?t=2477285). If you could retrieve a "debug" version of Secure Boot Policy from your EFI partition then it means that Secure Boot has just disabled itself on your tablet. It's highly unlikely, however, since you weren't able to run desktop apps in your original 8.1 install...
Click to expand...
Click to collapse
I copied a SecureBootDebugPolicy.p7b (dated 02/13/2014 @ 3:19PM) file from there. From what I was reading, I take it that's a good thing? (click thumbnail for full pic)
SecureBootDebugPolicy in the certificate manager tool
what is the icon that next on the left of action center (bottom-right, triangle flag) and at the right side of OneDrive?
hisoft said:
what is the icon that next on the left of action center (bottom-right, triangle flag) and at the right side of OneDrive?
Click to expand...
Click to collapse
USB/SD eject (I have SD card I keep in the slot for extra storage)
thesawolf said:
USB/SD eject (I have SD card I keep in the slot for extra storage)
Click to expand...
Click to collapse
Good job ASUS :good:
If you were able to retrieve a SecureBootDebugPolicy.p7b that is functional, it probably means that there was a Debug policy on your device at some point? (ref. Original Thread on ASUS). I've just looked into my Surface RT and there's a file with that name too, but it cannot be opened (it's simply an empty 0-byte file) and probably you're another lucky one who has a debug policy. (However it can't be explained why Get-SecureBootPolicy shows that you're using a production policy? Does it show the production policy GUID that TechNet says is normal, or something else? Policies don't disable secure boot, Confirm-SecureBootPolicy showing true is perfectly normal even in debug.)
Would it be possible to share this SecureBootDebugPolicy.p7b and then we'd able to see if there is someone else with a VivoTab RT that could test it? I assume it's locked to your device but it's always worth a try.
Could anyone else with experience working with Secure Boot look into this? While it's probably a lucky isolated case, it's nevertheless promising...
Just to double check: does anybody else have a Vivo Tab RT with 8.1u1 they could check this against? It would be amazing / hilarious if the update disabled signature enforcement. The question would then be whether that was Microsoft's idea or Asus's...
Oh, and one other quick test: grab a built-in program (CMD.EXE or Notepad.EXE, for example) and make a copy of it to somewhere you can edit it (like the desktop). Open the file in a hex editor (if needed, copy it off the tablet first) and change something unimportant, like a few characters in a string (not a file path, more like "is not recognized as an internal or external command..." or some such thing) to some other value that has the same number of characters. Save the file and try running it on the tablet again. The idea is that this will be an EXE with an *invalid* signature (as opposed to just being unsigned) and that would be very surprising if it works... but this whole thing is surprising!
GoodDayToDie said:
Just to double check: does anybody else have a Vivo Tab RT with 8.1u1 they could check this against? It would be amazing / hilarious if the update disabled signature enforcement. The question would then be whether that was Microsoft's idea or Asus's...
Click to expand...
Click to collapse
Tried it on a VivoTab RT LTE (AT&T) with u1 -- ran 7z ARM and it failed on signature verification.
I would never run another update on that device. Don't want to patch up the botched update.
Sent from my Z10 using XDA Premium 4 mobile app
I wonder if there's some way to take a full image of your current installation (possibly using a backup utility?) that can be restored onto other peoples' tablets. Even better would be if the relevant bits could be extracted from your image and carried over to other tablets (such as Surface RTs, Surface 2s, Lumia 2520s, etc.) but that may be harder. Still, worth investigating more...
Was it new or used when you got it? And if it was used, is it possible the original owner JB'd it and it stuck through the update?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
GoodDayToDie said:
I wonder if there's some way to take a full image of your current installation (possibly using a backup utility?) that can be restored onto other peoples' tablets. Even better would be if the relevant bits could be extracted from your image and carried over to other tablets (such as Surface RTs, Surface 2s, Lumia 2520s, etc.) but that may be harder. Still, worth investigating more...
Click to expand...
Click to collapse
Should be able to use dism.exe. Not sure if it will capture the online image, but you can definitely use it in recovery mode. Should be able to capture with new-windowsimage too. Going to try it out real quick and report back... I would choke puppies for this image.
---------- Post added at 11:24 AM ---------- Previous post was at 10:35 AM ----------
Okay it you can't capture the online image. You'll need to have a USB drive with enough space to capture the whole thing. Make sure you either suspend bitlocker or make sure you have a copy of the recovery key handy (It's 48 decimal digits).
Boot to the recovery partition (it doesn't matter if it's on the local storage or a USB key - it can even be the same USB key you will copy the disk image to if you have enough free space).
Choose language, troubleshoot, advanced, command prompt (I think - point is, you want a command prompt).
Verify the drive letters are what you expect them to be (internal storage is c, usb disk is d, ramdisk is x).
run: dism /capture-image /ImageFile:d:\winrt81u1.wim /CaptureDir:c:\ /Name:WinRT81U1vivotab
Let it finish. It will take a while. Probably a long time since it's writing to USB 2.0 flash storage. Bet on an hour. You probably want to make sure it's plugged in to power (but you're not writing anything to the local storage, so you won't break anything if it goes dead).
Upload that wim file to skydrive and share it with me!
Sjflowerhorn said:
Was it new or used when you got it? And if it was used, is it possible the original owner JB'd it and it stuck through the update?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That is impossible, the 8.0 jailbreak was performed in memory and it not written to the disk.
Toxickill said:
That is impossible, the 8.0 jailbreak was performed in memory and it not written to the disk.
Click to expand...
Click to collapse
Gotcha, I haven't JB'd mine yet, so I have no idea how it works. Apparently I'm Windows ShmeShmarted and can't make a bootable flash drive that contains the rollback. And coming from android devices where everything sticks except for some very select mods/devices I just figured it might be possible.
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Sjflowerhorn said:
And coming from android devices where everything sticks except for some very select mods/devices I just figured it might be possible.
Click to expand...
Click to collapse
Believe me, that's what all RT owners would WANT to have. Although there's many reasons to jailbreak a device, I personally prefer feeling like I've gained full control of hardware I own. The in-memory jailbreak was good, but it didn't have that satisfying feeling of permanence you often get with an Android rooting / OS replacement.
southbird said:
Believe me, that's what all RT owners would WANT to have. Although there's many reasons to jailbreak a device, I personally prefer feeling like I've gained full control of hardware I own. The in-memory jailbreak was good, but it didn't have that satisfying feeling of permanence you often get with an Android rooting / OS replacement.
Click to expand...
Click to collapse
Until the carrier gets to your device and locks the bootloader (AT&T)
I actually preferred the in-memory jailbreak in many ways. It meant we couldn't modify system files or run unsigned code for a couple minutes after boot, but it also meant we could trivially easily "un-jailbreak" and we could install updates with no fear of them destroying anything. Even the huge 8.1 update, which broke the jailbreak *process*, could be started on a device which was already jailbroken without causing any harm (unlike, say, many iOS jailbreaks).
I agree. I liked that the 8.0 jailbreak wasn't permanent but also exceedingly simple to install at boot. It meant that sending my Surface RT back to my Microsoft under warranty had no problems at all.
Lumen_Melano said:
I agree. I liked that the 8.0 jailbreak wasn't permanent but also exceedingly simple to install at boot. It meant that sending my Surface RT back to my Microsoft under warranty had no problems at all.
Click to expand...
Click to collapse
The in-memory Jailbreak is great when you hard brick your Surface and take it to the Microsoft Store. They just gave me a new one with no problems at all.
Hi everyone,
I've done a quick "port" of Tiny8086+ emulator for Windows RT and it's now in Windows Store: http://apps.microsoft.com/windows/en-GB/app/8086tinyrt/cf962b90-7c3a-448f-9932-a37432e9595b
To use the app, you'll need to have keyboard and mouse with your Windows 8 tablet. I didn't have time to optimize user interface for touch and I'm sure it has also a lot of missing bits and pieces I've also removed some of original 8086tiny+ advanced features (like debugger, tcp/ip serial).
Anyway, main purpose of app to provide entertainment of playing those old games on Windows ARM tablet. I've also put up some instruction in here, in case you ran with trouble with app.
Hi!
Nice! I have installed on my surface. I can move the mouse and navigate through menus, but I can not enter any input on the console. I can not see also any log on screen, is getting stuck or it takes long time to start?
I have the TypeCover and also a bluetooth trackpad/keyboard, but none of them works.
Thanks!
jesuslg123 said:
Hi!
Nice! I have installed on my surface. I can move the mouse and navigate through menus, but I can not enter any input on the console. I can not see also any log on screen, is getting stuck or it takes long time to start?
I have the TypeCover and also a bluetooth trackpad/keyboard, but none of them works.
Thanks!
Click to expand...
Click to collapse
To me it sounds like emulation (of operating system e.g. FreeDOS) weren't started at all (emulation won't auto start when tiny86rt app is launched). And of course nothing will happen, if you type in keyboard, until emulated OS (e.g FreeDOS) is running.
Can you check the tutorial video and verify, that you have first selected correctly both bios and floppy image, and then started emulation by clicking Emulation -> Reset (boot FD). Are you using FreeDOS disk images or what? Anyone else having issues on Surface(RT) + touch/type cover combo?
noxo said:
To me it sounds like emulation (of operating system e.g. FreeDOS) weren't started at all (emulation won't auto start when tiny86rt app is launched). And of course nothing will happen, if you type in keyboard, until emulated OS (e.g FreeDOS) is running.
Can you check the tutorial video and verify, that you have first selected correctly both bios and floppy image, and then started emulation by clicking Emulation -> Reset (boot FD). Are you using FreeDOS disk images or what? Anyone else having issues on Surface(RT) + touch/type cover combo?
Click to expand...
Click to collapse
Hi,
It's probably my fault, I thought it came with a pre-loaded OS, I will check the tutorial
Update:
I have tested with your tutorial, and when I tap boot from FD, the app is crashing.
Thanks!
jesuslg123 said:
Hi,
It's probably my fault, I thought it came with a pre-loaded OS, I will check the tutorial
Update:
I have tested with your tutorial, and when I tap boot from FD, the app is crashing.
Thanks!
Click to expand...
Click to collapse
Interesting, I haven't managed to crash it yet with any image (even when mixing bios and fd image).. are you using bios_cga.img and fd.img from http://jaybertsoftware.weebly.com/uploads/3/0/2/1/30218655/8086tiny_plus_1_34_win32_sdl.zip?
I've tried app both with x86 (Macbook + Haswell i5) and ARM (Dell XPS 10 + Snapdragon S4) devices without any crashes What if you try to
reinstall the app, in case some invalid image data were copied to apps temporarly folder?
noxo said:
Interesting, I haven't managed to crash it yet with any image (even when mixing bios and fd image).. are you using bios_cga.img and fd.img from http://jaybertsoftware.weebly.com/uploads/3/0/2/1/30218655/8086tiny_plus_1_34_win32_sdl.zip?
I've tried app both with x86 (Macbook + Haswell i5) and ARM (Dell XPS 10 + Snapdragon S4) devices without any issues.
Click to expand...
Click to collapse
Hi,
Yes, I have:
- downloaded that .zip file
- unzip it
- rename the bios to .img
- load both files on the app
- start with FD
But It is crashing always. Any idea?
Thanks,
Jesus.
jesuslg123 said:
Hi,
Yes, I have:
- downloaded that .zip file
- unzip it
- rename the bios to .img
- load both files on the app
- start with FD
But It is crashing always. Any idea?
Thanks,
Jesus.
Click to expand...
Click to collapse
Can you try reinstalling app, and checking that you'll select bios_cga.img for BIOS image and fd.img for FD image? Is it Surface Pro, or Surface 1/2 RT?
noxo said:
Can you try reinstalling app, and checking that you'll select bios_cga.img for BIOS image and fd.img for FD image? Is it Surface Pro, or Surface 1/2 RT?
Click to expand...
Click to collapse
I have already done that, I though maybe it was keeping on memory a wrong file or something, so I did it before. It is a Surface RT (1)
jesuslg123 said:
I have already done that, I though maybe it was keeping on memory a wrong file or something, so I did it before. It is a Surface RT (1)
Click to expand...
Click to collapse
Hmm, that's weird. Maybe there are some Spanish characters in path or folder path is too long which will then fail loading of disk images.. or something with Surface RT 1, however hardware wise XPS 10
has even lower specs..
One more check I can suggest, is to check that if bios and disk images were correctly copied to C:\Users\<UserName>\AppData\Local\Packages\xxxxx8086TinyRT_xxxxx\LocalState folder. You can also try manually copying them there, if those two files does not exist and see if it helps
Do you have Windows 8 desktop you could try the app?
noxo said:
Hmm, that's weird. Maybe there are some Spanish characters in path or folder path is too long which will then fail loading of disk images.. or something with Surface RT 1, however hardware wise XPS 10
has even lower specs..
One more check I can suggest, is to check that if bios and disk images were correctly copied to C:\Users\<UserName>\AppData\Local\Packages\xxxxx8086TinyRT_xxxxx\LocalState folder. You can also try manually copying them there, if those two files does not exist and see if it helps
Do you have Windows 8 desktop you could try the app?
Click to expand...
Click to collapse
The files are there. Please check the attached screen capture
Thanks,
Jesus.
jesuslg123 said:
The files are there. Please check the attached screen capture
Thanks,
Jesus.
Click to expand...
Click to collapse
I managed to reproduce the crash. It's about the nonascii charaters (รบ) in your username, which will cause the crash. I'll try to fix that on weekend Thanks for testing.
App is now updated and available in Store. Verify that you're running version 1.1.92.5 (from Charms bar -> Permissions) after installation. Pls report, if it still crashes
noxo said:
App is now updated and available in Store. Verify that you're running version 1.1.92.5 (from Charms bar -> Permissions) after installation. Pls report, if it still crashes
Click to expand...
Click to collapse
Working fine! Nice
One question, my attached keyboard is Spanish, by free dos seems to be running on english mode, is that due to free dos or emulator settings?
Thanks!
jesuslg123 said:
Working fine! Nice
One question, my attached keyboard is Spanish, by free dos seems to be running on english mode, is that due to free dos or emulator settings?
Thanks!
Click to expand...
Click to collapse
You won't get Spanish keyboard fully working, reasons for that are long to cover fully here It's bit of a fault in everywhere, in modern keyboards vs old XT world, in freedos, bios image and emulator keyboard handling via SDL backend. Things might a bit better, if you boot in MSDOS and type in "keyb sp" command to load keyboard layout manager TSR, but I'm sure not all keycombos (like ALT+GR + key) works etc.
Anyway, Have fun!