Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

UCyborg

Member
  • Content Count

    678
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    8

UCyborg last won the day on September 8 2019

UCyborg had the most liked content!

Community Reputation

202 Excellent

3 Followers

About UCyborg

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

3,402 profile views
  1. qBittorrent 4.1.9.1 is the last version that runs on XP. Edit: Never mind, was already mentioned I see. I just noticed today.
  2. Delete the :80 part in the address bar and it'll work.
  3. I needed to reformat my USB flash stick to make it bootable on UEFI system. Having no spare one and having data on my existing one, I decided to just dump it, block by block to an image file on a disk and restore it later. Was going to use Linux and dd tool, but noticed ImDisk on my Windows install has the option to save content of the drive to image. I initially went with defaults, but then thought that maybe I should've ticked checkbox that saves MBR as well. At least that's supposed to produce the result that I would've gotten with dd anyway I imagine when simply specifying source (entire device, eg. /dev/sdX) and destination without any extra parameters. So I cancelled it and suddenly the drive wasn't readable anymore. I said I'll worry about what's gone wrong later, cloned it with dd, used the drive for that thing I was going to use it for, then restored the image I've made earlier. I ran chkdsk on it, which found and fixed a bunch of errors. One file at least got messed up, but at least it's readable now. My question is, is there a rational explanation for why it's just gone bad? A software glitch? I'll probably run badblocks' read-write non-destructive test on the drive in the near future, but not today, just in case to see if anything pops up.
  4. It probably has to do with hibernation file not being the sufficient size, a problem that was likely inherited from the old Windows 7 installation. I suspect hibernation/hybrid sleep didn't work on that particular Windows 7 installation. Windows 10 just changes "shutdown" to "log off and hibernate", aka. "fast boot" by default, so the issue showed up and then disappeared with disabling fast boot. I have a Win7 install with that problem, but I don't know why the size wasn't set right in the first place (or maybe the default just doesn't work correctly under certain circumstances). I just turned hibernation off so it can go to sleep (and saves some disk space). If power outage occurred during sleep, it would cause the session to get lost since it's not backed up to disk. Hybrid sleep feature (can be turned off without disabling hibernation) is also the reason such transitions are much slower by default than they are on Vista predecessors. Maybe it's better if system is loaded on SSD disk.
  5. Back to Android, besides using the app, it's possible to manipulate several files to achieve the desired effect (root needed, assuming Linux kernel in use has USB mass storage functionality compiled in): /sys/class/android_usb/android0/enable - write 0 or 1 in here to disable/enable USB functionality (needs to be disabled to be able to write to other files). /sys/class/android_usb/android0/f_mass_storage/lun/file - write the path to block device that you want to expose through USB mass storage, external SD card's first partition should be /dev/block/mmcblk1p1 /sys/class/android_usb/android0/functions - USB functions to enable, some possible values are mtp, mass_storage and adb. Multiple values can be separated by comma. su echo 0 > /sys/class/android_usb/android0/enable echo /dev/block/mmcblk1p1 > /sys/class/android_usb/android0/f_mass_storage/lun/file echo adb,mass_storage > /sys/class/android_usb/android0/functions echo 1 > /sys/class/android_usb/android0/enable These commands (need Terminal Emulator app) will make SD card appear just like any USB flash drive on the computer and enable ADB support at the same time (equivalent to having USB debugging checkbox ticked in developer settings on the phone). It's a good idea to unmount SD card in the storage settings first, though depending on the usage (eg. only reading from it), one might be able to get away without unmounting it and causing havoc on the card's file system.
  6. It looks like clearing old entries in Device Manager that was setup by INF file that came with those drivers from Windows Update, deleting said drivers, setting up fastboot device entry using device update wizard and picking built-in ADB Device helped with the issue of the said device entry for fastboot mode being reset under certain circumstances. I plugged the phone with ADB enabled with the same OS builds and recoveries I was experimenting with the last time and cannot reproduce the issue anymore when rebooting into fastboot mode afterwards.
  7. 1909 doesn't download Candy Crush with default settings. Settings app is still clunky and buggy, tends to hang if you minimize it and crashes at times. Control Panel never had such issues. MS started to even hide Win32 application crashes about 1-2 years ago with default settings. Even if you have debugger registered, you don't get the opportunity to attach it at the moment of the application crash. Was it to not scare the average Joe? Homegroup remnants are still lurking (Give access to sub-menu in file/folder context menu). Supposedly next year's build for the masses will rid of them. They fixed the initial delay from 1809 when opening New sub-menu for creating file. Also, it would make more sense for notification center to open on the screen on which the taskbar with the button to open it resides, plus an option to show notification area on other taskbars would be nice. If 3rd parties can do it, surely MS could too and have it neatly integrated into the shell. Oh well.
  8. I'd try clearing the traces of the old drive from Device Manager and running diskpart from the administrative Command Prompt and typing in automount scrub and rebooting the system.
  9. Correct. The device ID when in fastboot mode is VID_0FCE&PID_0DDE, so that *.inf couldn't help the OS detect it as compatible with the driver. But you can still set it for use with fastboot mode by manually selecting it in driver update wizard. Yup, yes to all questions. Already got it to work that way. It's good that at least for ADB mode, it works out of the box either way. Though by default settings, OS might still see fit to download "drivers" from Windows Update, even though no specialized driver is usually involved since it's all just about the .inf file identifying and setting up the device to be driven using winusb.sys.
  10. Thanks, I didn't look in system winusb.inf and manufacturer supplied INF must have been downloaded from Windows Update, placing the entry in Device Manager that usually appears under Universal Serial Bus devices under a different category, so I didn't realize it was already supported out-of-the-box. I use Win10 versions 1809 and 1909 on my two machines. Depending on the software currently running on the phone, hardware ID differs, so who knows which is the "right" one. Vendor ID is always VID_0FCE, as should be. That problem requiring re-install was actually encountered when putting the phone in fastboot mode. I suspect a conflict happened due to an old entry having a different compatible ID (adb vs fastboot and the fact that fastboot ID is missing from winusb.inf), but the same vendor and device ID. The ID when in fastboot mode is constant, but otherwise it seems to depend on the OS running, even though it should be constant as well as long as we're talking about the same phone model, in this case Xperia E3. I did some cleaning up in Device Manager and removed two drivers that were downloaded from Windows Update for ADB, so now I have phone's entries under Universal Serial Bus devices, not under some custom categories like before. I also added USB\Class_FF&SubClass_42&Prot_01 ID to the list of Prevent installation of devices that match any of these devices ID group policy, so the OS won't try "updating" them. Manually installing ADB Device through update wizard in Device Manager while phone is in fastboot mode also works and makes it visible to fastboot utility. If I encounter that problem again with fastboot mode requiring driver re-install, maybe I can just add the USB\Class_FF&SubClass_42&Prot_01 ID to the CompatibleIDs value under device key in registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB in hope to prevent it in the future.
  11. I found this, which isn't really universal since it defines a bunch of specific device IDs to identify them and is outdated anyway. There's also this pull request posted on that project's GitHub page and also another repo containing a dead link to already singed driver (or more precisely, signed INF that identifies ADB interface by the universal compatible ID). So what are my options? Anyone found such a driver/INF that can be just installed and forgotten about or do I have to go the signing the modified android_winusb.inf with self-signed certificate route if I don't want to disable driver signature enforcement and such? So far, my phone has used like 6 different device IDs to identify itself and under certain circumstances, I even have to re-install the official driver/INF for it to work again and confirming that I do want it installed, even if device ID doesn't match. Windows should really have universal ADB driver at this point, like it does for USB mass storage devices...
  12. I still don't get any glow on normal windows with TextGlowMode set to 0x3, even though it's there on ribbon-utilizing applications. I can specify the amount by saying eg. 0x000c0003.
  13. Approx. 2 years ago, I noticed the tray refusing to open. I only use that thing once in a blue moon, so I just left it back then. This summer, I finally poked into the designated hole to open it manually. Now it opens normally most of the time, except the first time after turning on the PC, when it only opens after second press of the eject button. The unit is almost 11 years old. As far as reading is concerned, that works.
×
×
  • Create New...