gilbosh elmerah philippa
Rosita Westhouse
Hi everyone, by the end of the last year, I started working on CGAView again.
Here's an experimental release that includes some improvements (hopefully) and support for the 640x400 mode.
It also supports crossloading so far, so you can, for example, display these hi-res pictures on normal CGAs, too.
Hi , I am ready to help test your files. I have Toshiba T3100e , and unable to start win (L.E. managed to start win2.03... work-in progress) and it seems that all EGA/VGA game requirements are out of my reach so... only CGA/Olivetti/AT&T remains.... Downloaded files now, will boot up system and give it a go.
FYI QB has a BIOS check before it allows SCREEN 4 to run. If you make this change to either QB.EXE/QBASIC.EXE or your compiled program, then 640x400 will work on "Super CGA" Compaq/Toshiba systems and DOSBox-X.
Maybe it's because the utility clears the screen during start and then sets plain text-mode.
- Which in turn might not be supported in CGA machine mode, if it's MDA-specific (there's a separate machine mode for MDA).
The updated utility now does use CGA's high-resolution graphics mode instead. I know, it's just a temporary fix.
I would have also rather done it right, but I'm a bit busy right now (life and things). Hope you don't mind.
You select a VGA or VGAONLY machine setting in config file, start DOSBox-X and type DCGA at command line prompt.
That will turn the graphics system into an Olivetti/AT&T compatible mode. I've tested it with latest CGAView X, too.
I can see parallels here to DOS/V (/V=VGA) of the early 90s here: DOS/V also had two select-able display modes.
On MS-DOS version, its very easy to do. Typing "US" will activate English mode, while "JP" will activate Japanese mode.
The TOSHIBA Eco Charge Mode increases the battery life cycles by not charging to full capacity. This mode is recommended for users who most often use the PC with the AC adapter. The battery life per full charge is shorter in this mode. This mode is enabled/disabled through "Battery Manager".
If you enable this mode, you need to discharge the battery to approximately 50% at least once without plugging in the AC adapter. Failure to do so will result in eco charge mode not being enabled, and the battery life cycles will not increase.
In the battery manager window you will be instructed to discharge the battery to approximately 50% at least once without plugging in the AC adapter. Failure to do so will result in eco charge mode not being enabled, and the battery life cycles will not increase.
I am trying to get Ubuntu 14.10 to boot on my Toshiba Satellite C55D-B5212. I have UEFI boot mode and Secure Boot enabled. The Ubuntu live USB stick booted without issues and the install seemed to go through without any issues. However, when I rebooted the laptop I got a message asking me to reboot and select the proper boot device.
Note that this includes a path to a file, starting with the hard disk (HD(...)). Yours lacks that, which suggests some sort of problem. You might try manually adding a boot entry with efibootmgr in Linux, as in:
This command should create a new entry called MyUbuntu. Note the doubled-up backslashes (\\) used as directory separators in the path to shimx64.efi. After you type this command, use efibootmgr -v to view the results; you should see a new entry that includes the path to shimx64.efi, and its number should be first on the BootOrder line. If that all looks good, then reboot and hope it works.
If the boot fails at this point and efibootmgr -v shows that the entry you created has changed, you could try creating the entry in an EFI shell program. This process is a little involved, but in brief:
If this procedure fails, then your firmware is very badly broken. If the computer is brand new, I recommend returning it to the store and contacting Toshiba to tell them why you returned it. Manufacturers will keep selling junk if people don't complain, and returning junk is the only way we have to complain that will get any attention at all.
If the above procedures fail and you can't return the computer, you could try copying the contents of EFI/ubuntu on the ESP to EFI/Microsoft/Boot (you'll need to create that directory) and rename shimx64.efi to bootmgfw.efi. You may then need to create a boot entry with efibootmgr or bcfg, as just described. As you might guess, EFI/Microsoft/Boot/bootmgfw.efi is the usual name of the Windows boot loader. Unfortunately, some badly broken EFIs won't boot anything else. Boot Repair can also set this up, although I believe you need to select an option on the Advanced menu to do it.
i am not sure if you are familiar with other Home-Assistent Integrations, but it is usual to use a default card, like in this the climate, bridge the functionality over to the device and let user modify it using othe custom cards.
having said this: icons are HA default, same is (i think) the power button behaviour and the colors. the default silent mode should be available in the fan speed selection. special modes like pureion and eco etc. are not yet implemented.
2021-09-02 12:19:50 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration toshiba_ac which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Is there any Logic presence already for offline units ? At this moment 1 unit started to flash rapidly and Toshiba app Shows it has no connection, HA just shows as working with last values when it stopped working
It took me hours to get it to work, mostly because when inserted in my PC, I was not able to write anything to it. Reflashing of the Cards FW solved the writing issue. I have a Link on my Desktop where I can drag and drop files to the card via Wifi.
Setup 1 - Desktop + flashair = OK
For testing I inserted the toshiba wifi SD into my desktop (AP mode). I can detect the wifi using both handphone and desktop. Using the desktop i can write/read files wireless into the SD card
There may be other ways to set up the card, but this config works for me.
This config makes the card work as a network drive with read/write access to the root of the drive.
Remember to enable FlashAir in Prusa firmware.
I assume full size.. I am in the process of building a MK3 and planned to go down the Pi Zero route with Octopi, but there are so many problems right now, I need to find an alternate solution and am thinking of getting a FlashAir card.
Can I check something about how it works.. Can the card register to my router and get an IP address.. And then I can access it from every device on the network? Or is it just peer-2-peer Wifi meaning that it can only connect to one device.
I played with mine yesterday - i have w03 (16GB), i bought it used. I just couldn't get it to work on different IP subnet than 192.168.0.x. No matter what i did it just wouldn't connect unless IP of my router was in that range. i've had my IP in range 10.x.x.x and i've had to change aaallll my devices because of that little bastard... ?
I can't seem to get the Mk2S firmware 3.1.0 working with a 16 GB W-04. I configured the card to connect to my AP and I am able to access the card and transfer files to it without any problems. So far so good. The printer however does not see the new files until poweroff/poweron.
I have enabled the FlashAir setting in the firmware. The support page does not show the IP address so I suppose the printer does not know that there is a wireless card and so does not re-read the filesystem before accessing the list of files.
OK, the card seems to work correctly if the gcode files are located in a subdirectory and not in the root of the card. In root it works if one gets into a subdirectory and then back. Sometimes I need to start rotating the select knob for the file to appear. If I delete a file sometimes a fake GCODE file name appears instead.
Unless the card itself is playing some tricks with committing the filesystem to be visible from the client I suspect that this is a firmware problem - which I can understand as it is hard to implement a consistent filesystem access if it can be changed outside of the firmware's control. Until this gets fixed I at least have a workaround.
I've recently picked up a Toshiba Libretto W100 and have successfully managed to install Arch Linux with openbox on it. Windows 7 is just too damn slow to use on this and is terrible in general.
For those interested, the device has only one USB port and two dual touchscreens, (looks like a tablet that folds in two). I managed to get Arch installed on this by using a powered USB hub (Logitech H-UE5) and plugged in an external keyboard and mouse as well as a live booting arch install usb.
Anyway I wanted to make use of the two buttons on the device, on Windows 7 the Toshiba software assigns these keys to have one act as a "home" to bring up a dashboard on touchscreen stuff and the other to bring up an onscreen keyboard.
I've installed Florence from the AUR and wanted to assign one of the buttons to bring up Florence onscreen keyboard at least. The other button I've yet to decide what I want, maybe issue a command to rotate the screen to portrait mode?
When I issue the keys all I get in dmesg is this:
Finally I wanted to get the device to rotate the screen (by use of the accelerometer if possible), if not at least a script to rotate the screens should suffice. I was hoping to use this as a kind of E-Reader.
Not sure what I'm exactly doing with xrandr apart from reading up on what others have achieved with Ubuntu and other distros.
What would I need to do to get the accelerometer working?