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


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


cdob last won the day on September 25 2019

cdob had the most liked content!

Community Reputation

17 Good

About cdob

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

3,180 profile views
  1. Thanks for the testings and the report. I wasn't aware of this 2048 bytes sector feature in real world. What about the future? The mainboard may fail in some years. Swap the disk to another system? Swap the disk to a USB case? How to mount the partition then? Choose a choice depending on your situation. different data importance: data loss is acceptable or data loss is not acceptable. What to do with the 5 TB disk finally? Rely on a specific driver version? And use 2048 bytes sectors? Any chance to read the disk at another approach? Does a default Win10 DVD mount the disk? Does ntfs-3g support 2048 bytes sectors? Is there a parameter? The Asus M5A88-M provides a PCI slot still. A Promise PCI controller can be attached. This may be another chance. But: are there mainbords with PCI slot in future? Are there drivers? Or try another driver with 512 bytes per sector. This should be readable now and in future. Two partitons at MBR should provide each 2 TiB, sums to 4 TiB. About a CD data is missing from the 5 TB disk. No idea, if this is possible with default XP IDE drivers. Given average importand data: I would choose the 2048 bytes per sector. And create a 32 bit PE with the AMD drivers integrated. Second booting with data access is possible. I would igore a mainborad failure.
  2. What happens at IDE mode? Does device manger list a hard disk? Does disk manager list the hard disk? The Asus M5A88-M manual describes a SATA Block (Multi-Sector Trasfer) mode. Long shot, guessed: This leads to a assumption: may this creates the 2048 sectors at a 5 TiB disk at BIOS level? The Windows IDE driver fails at this? The AMD AHCI dirver support this? The default is [Auto]. Multi sectors are transferred. Do you use Auto mode? What happens at [Disabled] mode?
  3. There are new partitons at the new disk. The old \boot\bcd dosn't match the new disk. Booting fails. Another approach: use locate http://mistyprojects.co.uk/documents/BCDEdit/files/device_locate.htm Set locate at the source system. Clone the disk next.
  4. MBRview shows one partition with Num LBA: 2441879937 http://reboot.pro/topic/8734-tiny-hexer-scripts/ 2441879937*2048/1024^2 ~ 4769297 Stange, yes there are 2048 bytes per sector. If it's not the hot swap case, then there has to be another reason. This can be a driver, e.g. the previous referenced DiscWizard Extended Capacity Manager. If no one ist installed, then there are the ahci driver still. Does ahcix86.sys creates virtual 2048 bytes per sector, given a hard disk greater 4 TiB? Try, write the full disk. Be aware, if you swap this hard disk to another system, reading files may fail. Backup the data.
  5. Use 'Intel SSD Toolbox' to TRIM the SSD manually. Try a old version at Vista too. https://downloadcenter.intel.com/download/29205/Intel-Solid-State-Drive-Toolbox https://drivers.softpedia.com/get/HDD-SSD-NAS-USB-Flash/Intel/Intel-SSD-Toolbox-335.shtml
  6. Thanks for the confirmation. I got curious and asked myself about a challenge: Windows 10 1507 x64 and a Xperia Z3. Xperia Manufacturer offers Emma to flash a device. Emma dosn't use fastboot mode, flashmode is used instead. Emma does use a Gordons Gate driver ggsomc.sys, signed by 'Sony Mobile Communications AB'. https://developer.sony.com/develop/open-devices/get-started/flash-tool/download-flash-tool/ Sony dosn't offer a fastboot driver themself. https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/ Sony recommends android.com USB drivers, android.com recommends Sony OEM dirvers. Loop closed, no signed fastboot drivers. There is a custom build FlashTool Xperia Driver Pack, the hash catalog file dosn't match the .inf file, it's not signed. USB\VID_0FCE&PID_0DDE is a generic Xperia fastboot HardwareID. https://forum.xda-developers.com/showthread.php?t=2635830 https://github.com/johnantoni/fastboot-adb/blob/master/Win32/Drivers/ADB%2BFastboot/android_winusb.inf Back to Windows 10 1507. There is winusb.sys driver integrated. But neither ADB nor fastboot inf file. Xperia Z3: Both ADB and fastboot does work, by selecting winusb manually at device manager. To summarize this: Windows 10 1511 and later supports ADB out of the box. A signed driver is integrated. As for fastboot, select winusb manually at device manager.
  7. Just to confirm, there are XP and later manufaturer drivers. Most likely you used this one in the past. https://developer.sony.com/file/download/xperia-e3-xperia-e3-dual-driver/ The manufacuter so0109adb.inf file uses the same driver and settings for ADB and fastboot mode. winusb.sys is used in both cases. https://en.wikipedia.org/wiki/Android_software_development ADB and fastboot is a generic Android feature. Back to Windows 10 default files. No drivers added. ADB is installed out of the box. At fastboot select winusb.sys manually. Install Xperia "S1Boot Fastboot" device: Run device manager, goto "Other devices". Is there a "S1Boot Fastboot" device with a yellow question mark? Verify the Compatible Id "USB\Class_ff&SubClass_42&Prot_03" Select 'Update Driver', 'Browse my computer for driver software', 'Let me pick from a list of available drivers on my computer', 'Universal Serial Bus devices', Manufacturer: WinUsb Device / Model: ADB Device Confirm the 'Update Driver Warning' Is there a "S1Boot Fastboot" device at 'Universal Serial Bus devices'? It is used the driver winusb.sys?
  8. Which HardwareID do you use? Which Windows Build number do you use? Windows 10 default winusb.inf supports the ADB interface out of the box nowadays. If I recall correctly, ADB was missing in Win 10 1507, but was added later. Fastboot mode USB\Class_ff&SubClass_42&Prot_03 is not supported in winusb.inf.
  9. cdob

    Win7 and openGL

    No idea about a linux host. Yes, should be at home folder. Or download the tools files yourself https://packages.vmware.com/tools/esx/latest/windows/index.html It's 10.3 tools currently at ESX. Use the Workstation Tools CD: http://softwareupdate.vmware.com/cds/vmw-desktop/ws/15.5.0/14665864/windows/packages/ There is .tar image, expand the file. And connect the ISO file to a virtual CD drive.
  10. cdob

    Win7 and openGL

    Did you install the VMware SVGA drivers, included in the VMware Tools? Which graphic card is listed at device manager?
  11. A additonal hint: Windows 10 1803 home is supported up to November 12, 2019. https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet I would try a clean installation with Windesk9+3G_V2_Windows_10_1803x86_FAT32.iso And do a upgrade to 1903. Keep in mind: this is a automatic repair installation with preserving the user data. Read: technically a new windows 10 1903 installation. The Bay Trail drivers are automatically reused from the 1803 installation. Should work, may fail. Be aware, with a Bay Trail CPU, 1 GB RAM and a emmc drive: Expect a day to do this. 1909 is arround the corner. This is more like a 1903 SP1: updates, not a new windows installation. If 1903 works well, the 1909 should work too.
  12. @HadroLepton Which model number do you use? There are manufacturer "Windows Image & Treiber" https://www.odyshilfe.de/treiber Added: It's a Bay Trail hardware. Intel dosn't support this anymore, there are Windows 8.1 drivers. https://www.intel.de/content/www/de/de/support/articles/000006105/processors.html The 8.1 driver works at Windows 10 1803, may work or fail at Windows 10 1903 or later. There is a Windesk9+3G_V2_Windows_10_1803x86_FAT32.iso for the X610129 device. There are Bay Trail drivers included in boot.wim and install.wim. Create a USB Stick, use FAT32 filesystem. Install Windows 10. In case if you like to use more recent 1903 x86: There are no bay trail dirvers at a vanilla 1903 ISO, hence no internal keyboard. Try the drivers from the Odys Windesk9+3G_V2_Windows_10_1803x86_FAT32.iso use a USB OTG cable, a USB Hub, USB mouse and USB keyboard. Install the Bay trail drivers, the internal keyboard works now. Or try similar hardware. https://downloadcenter.intel.com/download/25311/System-on-a-Chip-SOC-Driver-Package-for-STCK1A32WFC https://downloadcenter.intel.com/download/26693/NUCs-System-on-a-Chip-SOC-32-Bit-Driver-Package-for-Intel-NUC
  13. MBR USB boot testings: Some real world testings at a Thinkpad X230. Given a 3 TB USB hard disk with 512e bytes per sector. Three partitions: USB_BOOT, USB_2TB, USB_data USB_BOOT: a primary active FAT32 8 GB USB_2TB: NTFS 2 TB, within first 2 TiB of the hard disk USB_data: NTFS, behind 2 TiB 13 80 0 32 33 1023 254 63 2048 16580608 16582656 partition end sector on disk 7 0 1023 254 63 1023 254 63 16582656 4278384632 4294967288 partition end sector on disk 7 0 1023 254 63 1023 254 63 4294967288 1565499400 5860466688 partition end sector on disk 5860466688 sectors on disk BIOS mode, grub4dos geometry (hd0) drive 0x80(LBA): C/H/S=267350/255/63 Count/Size=4294967289/512 Partition num: 0, active, Fileystem type is fat32, partition type 0x0C Partition num: 1, Fileystem type is ntfs, partition type 0x07 Partition num: 2, Fileystem type is unknown, partition type 0x07 cat --hex (hd0)4294967296+1 correct hexdump, does match the hard disk sector. The BIOS reads up to 2 TiB. cat --hex (hd0)4294967297+1 zero listed only, dosn't match the hard disk sector The BIOS fails above 2 TiB. Bios boot, installation is possible: Windows 10 files at first partition Windows 10 \boot and \sources\boot.wim at first partition, \sources\install.wim at second partiton Windows 10 \boot and \sources\boot.wim at first partition, \sources\install.wim at third partiton: PE reads the whole disk Windows 10 \boot at first partition, \sources\boot.wim at second partition, \sources\install.wim at third partiton: \boot\bcd is adjusted to read \sources\boot.wim at the second partition booting fails: bootmgr message: A required device isn't connected or can't be accessed. Windows 10 \boot at first partition, \sources\boot.wim and \sources\install.wim at third partiton: \boot\bcd is adjusted to read \sources\boot.wim at the third partition Yes, the BIOS dosn't acces the whole disk, hence the bootmgr message. There are the equal results at UEFI boot. Even at UEFI moode, the first 2 TiB can be accessed only. There is either a UEFI limitation or bootmgfw.efi is limited. There may be other UEFI results at another hardware.
  14. There is a special BIOS. Use a adjusted ntdetect.com https://web.archive.org/web/20060302092406/http://www.911cd.net/forums//index.php?showtopic=14181
  15. At NT times, set the path to batch.cmd drive and path: batch.cmd cd /d %~dp0 or another relative path cd /d "%~dp0..\folder" cd /d "%~dp0folder" Does this works still?
  • Create New...