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. 


deomsh

Member
  • Content count

    53
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

9 Neutral

About deomsh

  • Rank
    Deomsh

Profile Information

  • OS
    98SE
  • Country

Recent Profile Visitors

1,587 profile views
  1. Windows 3.1 hangs on splash screen

    I solved my earlier incompatibilities between my two legacy BIOS's (spontaneous reboots with some partition types) and not starting Windows 3.1 in Enhanced mode with temporary swapfile if booted from another flash drive or floppy drive. It seemes to be DOS-related, I will explore that later. I made as a first start a FAT16 USB-HDD with RMPrepUSB, which resulted in an unintended experiment. This USB-HDD has two partitions, a normal one and a very small one with Partition ID 21 (a reserved partition ID). During setup, Windows 3.1 gave a pop-up screen with following text. "The partitioning scheme used on your hard disk prevents the creation of a permanent swap file. You can create a temporary swapfile". The last was not true in case of my USB-HDD: no starting in Enhanced mode with temporary swap file. As soon I set the partition ID of the second partition to 00 or 01, everything was back to "normal". I only found that this could be a "check" because of possible bootsector virus. https://books.google.nl/books?id=d3AlDwAAQBAJ&pg=PT188&lpg=PT188&dq=partition+scheme+used+on+your+hard+disk+prevents+the+creation+of+a+permanent+swapfile&source=bl&ots=sVtXOf5VFy&sig=80Pzvtwm7DrGG7m5cPCGSYi-tRk&hl=nl&sa=X&ved=0ahUKEwil06mLgInbAhVCsKQKHa__CP0Q6AEIJzAA#v=onepage&q=partition scheme used on your hard disk prevents the creation of a permanent swapfile&f=false BTW: the pop-up above seemed not to be MS-DOS-version related (I tried MS-DOS5.0 and MS-DOS 6.22 too). After that I made a few dozens of new installations on different USB flash drives with both my two legacy BIOS's. The only results I want to mention: On a FAT16 (06) partition a permanent swap file was possible (in case of MS-DOS 7.1 the peculiar drive must be unlocked with "LOCK [Drive]:") In case of two normal partitions on a USB-HDD only the Partition type of the partition where Windows 3.1 was started from "rules". If installed on a FAT (06) or FAT32 (0B) partition there were no problems, even if the temporary swap file resided on a FAT16X (0E), or FAT32X (0C) partition. Not the other way round, which is consistent with my earlier reports. Concerning the "partitioning scheme" error, I found Q82373. https://jeffpar.github.io/kbarchive/kb/082/Q82373/ BTW To be sure I repeated my experiments on a 3.2GB HDD: I could reproduce the "partitioning scheme" error, but on the HDD there was NO PROBLEM using a temporary swap file instead and starting in Enhanced mode from a FAT32X/0C partition. So maybe this error is a dead end.
  2. Windows 3.1 hangs on splash screen

    I am sorry if I wasted time. I am using four different USB flash drives and a small 16MB SD card for my experiments. I used RMPREPUSB already to make my FAT16 and FAT32 USB-FDD's (for my FAT12 one MKBT). I shall explore RMPrepUSB further, also other tools like Flashboot you mentioned in your last link. What I forgot mentioning from my latest experiments is that ALL eight Windows 3.1 (Express) installations gave exact same configuration files. Regarding the swapfile: I found in the Windows 3.1 Resource Kit that a "swap file" can only be made on drives with 512 byte sector-size (Windows Resource Kit, p. 245)
  3. Windows 3.1 hangs on splash screen

    I have red the link you mentioned. Although I do not really understand those BIOS-interrupts, I also red the advise that FAT32 / Partition ID 0B has "best compatibility". I am not sure its directly related tot the swapfile, but CHS/LBA unbalancing seems unlikely - as far as something can be said from experimental testing. On the P5 motherboard I have (some) access to, Partition Type OC with Paging disabled gave NO access to Windows 3.1 in Enhanced mode, the system rebooted directly! But on that board I cannot unplug the Windows 8.1 HDD's to see if that matters. I did three "experimentum crucis" with (maximum?) unbalanced partition table, with both Partition ID's 0C and 0B. Every test with re-format (FORMAT c: /Q /S) and a fresh Windows 3.1 (Express install). All six tests on the same 8GB Kingston Datatraveler flash drive. Motherboard Asrock 960GM-GS3 with AMI BIOS. CHS: 0/0/1&0/1/1; LBA 63/15647247. BIOS Legacy USB support ran fine, FORMAT and Windows installation too. Paging was only possible with Partition ID 0B. With OC: starting in Enhanced mode as soon Paging was disabled. CHS: 0/0/1&973/254/63; LBA 63/64. Same results. CHS: 0/0/1&0/1/1; LBA 63/64. Both Legacy USB support and FORMAT had no problem with this. Further: same results with this *exceptional* partition table. Boot Record values where always the same, except for the Serial Number. Sometimes the OEM Name changed after the first reboot. FORMAT wrote always "MSWIN4.1" as OEM Name, I have seen ""1MlerIHC", "1Mr,jlHC" and "1MnXTIHC" (without quotation marks). Rewriting to "MSWIN4.1" made no difference in the results, and was not changed again. Some nice PTEDIT-pictures from the third experiment, just before and just after re-format and after first reboot:
  4. Windows 3.1 hangs on splash screen

    Thanks a lot! I will explore grub4dos later. I tried both your CHS/LBA settings, including re-format, but made no difference. Windows won't start in Enhanced mode with Partition Type 0C (FAT32X) AND Paging enabled. When I disabled the temporary swapfile directly after I was back at the dos-prompt, no problems with this Partition Type. I also let Windows set the temporary swapfile to my regular FAT32 harddrive, made no difference.
  5. Windows 3.1 hangs on splash screen

    To be clear: I am not advocating to disable Paging us such. I only want to report my experimental findings regarding Windows 3.1 running from an USB Flash drive. In fact I think a FAT32 USB-HDD (Partition ID 0B) is the best choice using MS-DOS 7.1! In that case (and in case of FAT16 with Partition ID 06 of cause) Paging is at least possible if desired, or needed. I possess only two motherboards to run tests with USB-HDD/USB-FDD. My older boards are compatible to very small USB-FDD's only. It would be nice if a more experienced Windows 3.1/USB user reported DIFFERENT findings, testing with another Motherboard/Legacy Bios.
  6. Windows 3.1 hangs on splash screen

    I was puzzled why it was impossible for me, while booting from a floppy drive (loaded with MS-DOS 7.1) and starting Windows 3.1 in Enhanced mode from an USB flash drive partitioned as USB-HDD (with BIOS "USB legacy support" enabled of cause). This time the Partition ID of the USB-HDD made NO difference: 06, 0E, 0B or 0C - starting in Enhanced mode was ALWAYS impossible. I started booting from different USB flash drives, "set" to USB-FDD (FAT12, FAT16 and FAT32). Always with same results: impossible to start in Enhanced mode from an USB-HDD as C-drive. It was possible to install Windows 3.1 on my FAT16 USB-FDD (the FAT12 one was to small). While Windows 3.1 in standard mode was happily starting from an A-drive, in Enhanced mode it was not. FAT32 USB-FDD: same story. I somehow found out that disabling the temporary swapfile was here the "solution" (set Paging=0 in SYSTEM.INI [386Enh] and comment out PagingFile and MaxPagingFileSize). After that modification, starting Enhanced mode from the FAT16 USB-FDD was no problem anymore, the FAT32 USB-FDD gave same results. With Windows installed on an USB-HDD while booting from FAT12, FAT16 or FAT32 USB-FDD's and even from a floppy disk: Windows 3.1 started in Enhanced mode without any problem. With no swapfile, starting in Enhanced mode while booting my USB-HDD's with Partition ID 0E (FAT16X) or 0C (FAT32X): worked. In fact: anything goes! @MERCURY127. With MS-DOS 6.22 NOT the same story. Booting from a 2GB FAT16 USB-HDD and starting in Enhanced mode from the same drive was only possible for me with AND the Partition ID set to 06 AND without swapfile. With a temporary swapfile even the command prompt didn't return (in ALL my earlier tests at least the command prompt returned). With Partition ID 0E (FAT16X) MS-DOS didn't boot from an USB-HDD after the "Starting MS-DOS" message. Booting MS-DOS 6.22 from a 1.44MB (FAT12?) USB-FDD or from a regular floppy disk and starting Windows 3.1 in Enhanced mode from an USB-HDD gave same results in case of Partition ID 06. If the USB-HDD had the Partition ID 0E (FAT16X), this (primary) drive wasn't even visible from the MS-DOS 6.22 A-drive! Booting and starting in Windows 3.1 in Enhanced mode from a 120MB FAT16 USB-FDD A-drive: only possible without swapfile. BTW Trying to make a Temporary Swapfile on another drive with Windows 3.1 Control Panel gave a warning in case of MS-DOS 7.1: to protect Long File Names computer was halted, with a reference to the LOCK command needed for direct disk access. But using this command in a configuration that didn't start earlier before starting in Enhanced mode WITH temporary swapfile, made NO difference.
  7. Windows 3.1 hangs on splash screen

    I did some more experiments. With BIOS "USB legacy support" disabled and booting from a normal floppy disk loaded with a MS-DOS USB driver, there is no problem starting Windows 3.1 in Enhanced mode from a 8GB USB flash drive with Partition ID 0C (or from a 4GB one with a 2GB partition with Partition ID 0E). I had to revert to the original HP USB tool CHS-values (in case of the 8GB USB flash drive). The USB driver gave an error with the one-sector CHS.
  8. Windows 3.1 hangs on splash screen

    Same value, "14. Big Total Sectors: 15654785 (0x00EEDF81)". Here is the whole story (partinfo > HPUSBFW8.TXT) HPUSBFW8.TXT
  9. Windows 3.1 hangs on splash screen

    @Mercury: thanks for all suggestions. I don't use 32BDA, and since I use Windows 3.1 I don't have 32BFA (WfW only as far as I now, but I would be VERY happy if I'm wrong). I use IFSHLP.SYS only with MSCLIENT on my normal hard disk installation to have internet acces. I am perfectly happy with MS-DOS 7.1, so I have acces to my other FAT32 drives. The problem is about booting from an USB flash drive and if boot problems in Enhanced mode are related to the Partition ID. @Jaclaz: I did a really rude experiment by setting CHS to 1 sector, leaving the LBA values as the HP USB tool decided. My BIOS booted the 8GB USB flash disk without problems (Scandisk found no errors). Windows 3.1 showed the "normal" behavior: with Partition Type OC only booting in standard mode, after changing to 0B in Enhanced mode too.
  10. Windows 3.1 hangs on splash screen

    Total disk size is not given, see the uploaded picture. EaseUS Partition Master reports last sector = 15654847, so if first sector = 0 total will be 15654848.
  11. Windows 3.1 hangs on splash screen

    I already wrote down the partition table on my 8GB USB flash drive, partitioned with the HP USB Disk Storage Format Tool. Information from PTEDIT: Hard Disk: "Drive 1(7640MB); 974 cyl, 255 heads, 63 sectors per track. Partition table at sector 0 (cyl 0, head 0, sector 0). First Partition. Type=0C, Boot=80. Starting: Cyl=0, Head=1, Sector=1. Ending: Cyl=973, Head=254, Sector=63. Sectors: Before=63, Sectors=15654785. BTW: the other three partitions are empty. Partition Information: Fat32X, Bootable, 7643 MB. For the sake of experiment I changed "Type" to "0B" on the fly with PTEDIT, just after Windows 3.1 refused to start in Enhanced mode. Even without rebooting the computer Windows booted in Enhanced mode (Scandisk found no errors in between). I also tested FAT16 and Fat16X with a 2GB partition on my 4BG flash disk. Same results as with FAT32/FAT32X. With Partition Type ID 0x06 (FAT16) no problems booting in Enhanced mode, with 0x0E (FAT16X) booting in standard mode only. BTW: I've read your link, but I already tried changing OEM ID in the bootsector to "MSWIN4.1" if not there, made no difference according booting Windows 3.1 in Enhanced mode.
  12. Windows 3.1 hangs on splash screen

    I did some new experiments with the Partition Type ID. The partition manager I used (Minitool Partition Wizard 10, inside Windows 10) has the option to change the Partition Type ID. I took a fresh 4GB USB flash drive, created a 4GB partition, changed the Partition Type ID to 0x0C (FAT32X), formatted and made the partition active. With my Windows 98SE floppy disk (loaded with modified IO.SYS) I made the 4GB USB flash drive bootable, etcetera. Same result as with the HP USB Disk Storage Format Tool, Windows 3.1 booted ONLY in standard mode. I tested both motherboards again (960GM-GS3 and P5G41T-M LE). Afterwards I disconnected ALL my hard disks physically and started my good old PowerQuest Partition Magic 5.0 floppy disks. Partition Magic found NO partition errors on the 4GB USB flash drive (partitioned with Minitool Partition Wizard 10), and correctly identified the partition as 0x0C (FAT32X). I left Partition Magic and started PowerQuest's PTEDIT (resides on the first floppy disk). I changed the Partition Type ID to 0x0B (FAT32) and rebooted. Since Scandisk found no errors on the 4 GB USB flash drive, I tried to boot Windows 3.1 in Enhanced mode, and...... it worked. On both motherboards! BTW: using PowerQuest Partition Magic is potentially dangerous for disks partitioned with newer operating systems. So DON'T TRY THIS AT HOME!
  13. Windows 3.1 hangs on splash screen

    Lately I'd run into exactly the same problem as described above. I think I probably found the cause and the cure. So I decided to revive this old thread to report my findings. My 8GB USB flash drive was made bootable with the HP USB Disk Storage Format Tool. With patched IO.SYS and Windows 3.1 installed with modified WIN386.EXE. While USB legacy option was enabled in the BIOS of my motherboard I could boot into MS-DOS 7.1 without USB drivers. But Windows 3.1 could only be started in standard mode (win /s). In the meantime I had no problems booting Windows 3.1 in Enhanced mode from my hard drive. After many experiments, the whole problem turned out to be one of Partition Type. The HP USB Disk Storage Format Tool partitioned the USD flash drive as Partition Type 0x0C (FAT32X). When I, just for sake of experiment, changed the Partition Type ID with a partition editor to 0x0B (FAT32) and rebooted, Windows 3.1 started fine in Enhanced mode. According to Scott Mueller Partition Type 0x0B uses CHS, while 0xOC uses LBA. Obviously Windows 3.1 has problems with Partition Type 0x0C (FAT32X) in case of USB legacy mode (I tried two different motherboards from around 2010, same results). My hard drive is partitioned as 0x0C (FAT32X), so maybe the BIOS acts different in case of USB legacy mode and in case of a Hard Drive? My cure is to partition the USB flash drive with a decent partition manager that partitions the USB flash drive as FAT32 (Partition Type 0x0B) and not FAT32X. Further the partition has to be set to "Active". After reboot in MS-DOS7.1 the USB drive can be made bootable with "SYS [USB flash drive letter]:" (without quotation marks). Afterwards (with patched IO.SYS and WIN386.EXE) Windows 3.1 will be starting in Enhanced mode. BTW: I first thought this cure would only work below the famous 8.4GB barrier, but my partition manager even partitioned a 16GB USB flash drive as FAT32 (0x0B) and I was able to start Windows 3.1 in Enhanced mode from this drive. Maybe this can be BIOS specific.
  14. Win 98: Explorer in another language??

    Don't forget the backslashes: COPY C:\explorer.exe C:\WINDOWS
  15. Did you asked Watler for help? There is much possible by the config files.
×