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

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


cdob last won the day on September 25

cdob had the most liked content!

Community Reputation

17 Good

About cdob

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

3,024 profile views
  1. 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.
  2. cdob

    Win7 and openGL

    Did you install the VMware SVGA drivers, included in the VMware Tools? Which graphic card is listed at device manager?
  3. 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.
  4. @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
  5. 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.
  6. 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
  7. 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?
  8. Verify the used storage controller, use the AMD SATA controller. Boot XP at IDE mode, copy driver file ahcix86.sys and set registry. Set AHCI at BIOS next.
  9. Repair or remove programs in Windows 10: https://support.microsoft.com/en-gb/help/4028054/windows-10-repair-or-remove-programs Select the Start button, Settings and Apps.
  10. Can you uninstall the WinZip privacy protector app?
  11. Vmware Player does run a 32 bit XP system. A USB scanner can be passed from a 64 bin Win7 to the XP system.
  12. It's no the RAM itself, something before the RAM. E,g broken capacitors or power supply. At a old machine, capacitors may dry out, without a bulking head. Ignore the error so far, replace the hardware in future.
  13. There are some minor trouble, yes this can result to a BSOD 0x7e. Backup importand data first. Run a extended test at WD windlg.exe. If there is a question to repair at end of test, do the repair. https://support.wdc.com/downloads.aspx?p=3&lang=en
  14. Nvidia offers XP drivers still. Overall it's a hit or miss. May work or fail finally. XP should run at the EliteDesk 800 G1. However expect a driver hunting, may take some time. And exppect minor glitches, e.g. already mentioned missing USB3.0 Good luck
  15. https://support.hp.com/au-en/document/c03832938 HP EliteDesk 800 G1 Small Form Factor (SFF) PC Specifications Chipset Intel Q87 Express Windows XP is not supported by the manufactuer. XP should run at a Q87 in general, however it's a search for the drivers. SATA, chipset and network should be possible. Which graphic card is installed? No USB 3.0 drivers, change BIOS to USB 2.0 mode.
  • Create New...