![]() I can provide these on request, DR-DOS 7.03 is freeware afaik. In a hex editor, you can clearly see that all the data is there but the boot sector and FAT have been altered. The backup had all the files and etc, the version PCem mangled appeared blank. I then closed PCem and opened both a backup copy of the original I had made and the mangled copy in WinImage. Mindful of what you said about disks being ejected, I tried "putting it back in", and pressed enter, same message. This, if I may use very old terminology, may be a bit of a heisenbug.Īs a quick test, I removed my hard drive (so as to make sure I wasn't booting into Windows 95), booted my DR-DOS 7.03 floppy #1 image to the point where it was asking me to run FDISK but wasn't doing anything with the drive or really in general (sitting at a choice in a batch file basically), hit hard reset, and after rebooting was greeted with DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER. In short, absolutely nothing should be happening to the FDC while this is going on. Same if the hard drive is nonbootable and it's a nonbootable disk and I hard reset while it's waiting for me to strike the key to try again. I can literally put in a disk, go to the BIOS setup screen, hard reboot, and it will happen. I'm not having to "do" anything in particular in the emulator to make this happen. My hard drive is configured as 2048 cylinders, 16 heads, 63 SPT, for 1008mb. ![]() Voodoo Graphics is enabled at the moment, though as I haven't even gotten around to installing the drivers yet, I tried with it disabled as well and the same thing happened. I'm using a Tseng ET4000AX as the GPU, and a Sound Blaster 16 as the sound card, I haven't tested on different versions of either of those because after working around this issue through swapping floppy disks while the BIOS was on its "NO SYSTEM DISK PRESS ENTER TO RETRY" screen and installing Windows 95 I don't want to muck up the installation by changing hardware. It happens regardless of RAM settings but my current testbed has 16MB. ![]() It happens relatively consistently on an Award 430VX PCI motherboard, Intel Pentium (any MHz) or IDT WinChip (any MHz). Not immediately, but prior to the disk being accessed at boot time. The disk corruption happens during the BIOS after a hard reset. I'm afraid, however, that I find the actual code somewhat intimidating and will not be submitting my own patches.įor now, I'm installing Windows 95 in an emulated WinChip 133 (so as to avoid the floppy-killing) and plan on switching it to a Pentium 133 after install to see if there's any other issues. If you need any further testing from me, feel free. I realize this is very much in-progress code, and I'm simply reporting these issues so that they can be known and eventually solved. PCem becomes completely unresponsive at this point and is eventually killed by windows (your usual graying-of-the-window-then-reporting-to-microsoft crash box). When it crashes, CPU percentage drops to 2%, stays there, and PCem fills its pclog.txt file to several gigabytes. If NWCACHE is removed, you can get to a prompt, but randomly while doing disk accesses (even as simple as DIR), it will crash again. They consistently happen in the default DR-DOS install a few seconds after NWCACHE is loaded. If you want said log, I can try to take a look at it, but for obvious reasons at that size it won't load in say, notepad.Īs far as the crashes, they seem to happen during disk access. Secondly, DR-DOS 7.03 installs fine, but after install it occasionally freezes or crashes, filling pclog.txt to several gigabytes. I had this happen to DR-DOS images and a Windows 95 boot disk. ![]() It's hard to describe what I mean, but basically, when doing a Hard Reset, sometimes images in the floppy drive seem to get mangled to the point that they read as empty in WinImage and PCem and become no longer bootable if they were bpptable to start. I haven't tried a Dynarec'd 486 to see if they happen on a 486 yet, but they've been tested to happen frequently running a Pentium of any frequency.įirst off, floppy images are being "mangled" on reboot on occasion. I noticed some odd issues, which I'd like to report (Hopefully these aren't already known, but without a bug tracker I have to go by what's in this thread and I'm not seeing them)Īll of these issues only seem to happen in Dynarec mode. I got an emulated 286, 386, and 486 running and decided to compile myself a copy of the latest source code and try a Pentium 133. Hey! I'm a relatively new user of PCem but an old hat at emulation in general.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |