awkduck

They seem to have gone up in price, since I last looked. In US ebay $16+8 S+H. It looks like it has a special pad, that might be needed to use with it. I see a Win logo on the back of the box. Here

I see, "usb --int". Good to know that its there. I am sure it will come in handy on many projects :) The blinking cursor only happens from USB boot. But there are all kinds of strange things with USB. Even with an ext4 partition, syslinux cannot traverse the root directory. The same is true with grub4dos. If I have menu.lst and grubldr in /boot/grub, it cannot be found. Everything needs to be in root. I've never seen that before. I tried again booting the USB with a fat16 partition, using Dos mbr. When starting Win95 (no bootloader) it exits initiation and outputs "It is now safe to restart your computer" or something like that. Then if you reboot, the famous "c> cannot locate command.com". That probably is due to the fat16 partition not having the correct geometry. I've not had that issue when using a fat32 partition. There are many MBR/PBR to choose from. Do you mean one from the actual IDE partition? BTW, Zeroshell, is cool.

I've also thought about disabling detection, just to see that everything boots fine. If it did, has anyone configured devices without detection?

Your enthusiasm/ingenuity is in line with mine. The problem is that the only successful load, so far, is from ram. Nothing is saved after shutdown. Even if I configure everything on another machine, for booting on this one, the reboot clears everything. So if the task could just exit to Dos, then maybe I could copy the registry for some tweaking.

Thanks Goodmaneuver, I was thinking I should pick up a serial mouse anyway. Optical serial mice are cheap on Ebay. And the idea of an optical serial mouse amuses me.

Its a GeodeGX2, in a thin client.

The only time Grub4dos has an issue, is when direct mapping is used on the USB or IDE. If bootlace.com is used to install to the MBR(USB), there is a A20 error of some kind, and grub4dos fails. I am guessing this is because the device uses PS2 emulation over USB for the keyboard. This could be the same reason that when I use grub.exe from the prompt(USB), grub does not load the image (direct mapping). But memory mapping does work, as you are not tethered to the USB any longer. As you have said, Grub4dos has its own USB drivers. This is probably conflicting with the USB PS2 emulation in the device. menu.lst map --heads=16 --sectors-per-track=63 /80mb.img (hd0) #image is fat16 formatted with this geometry map --hook root (hd0,0) chainloader /io.sys If "map --mem --heads=16 --sectors-per-track=63 /80mb.img (hd0)" is used, then booting works; both from USB and IDE. But Win95 either disables the USB keyboard (PS2 emulation) or hangs, when detecting the USB. Either way, no configuration can be completed. I am having no issue booting with memory mapping. But, I cannot configure Win95 without a reboot. Once you reboot everything is lost. So I must either get direct mapping working, or prevent detection of only the USB. I do intend to eventually run from ram. But Win95 must first be configured and saved. Thanks for helping. But it may be a lost cause. I even considered booting Linux into ram, and running Win95 though Dosemu; with device mapping to the actually hardware. But Dosemu would be emulating the PCI Bus, so nothing I configured would apply to actual use on the direct hardware. Detection would resume as normal, with all of the same problems.

That is a great suggestion. Thank you, for joining in. Unfortunately, the device is a Single Board Computer and lacks external PCI/ISA slots.

From USB, grub4dos just sits with a blinking cursor (direct map). Memory mapped loads fine from there. Forgot to mention that renaming the inf folder has no effect.

Sorry for the late reply. It was a long day. Took awhile to get back at it. Thank you both, RainyShadow and Jaclaz. Rainy, you have a good point. I had not thought of that. But I do not have Ps2 connectors. Maybe if I order a serial/com mouse it would install that before the USB. Its been years since I've even owned a com mouse. I don't know how well 95 picks that up, during boot. Jaclaz, the booting over USB is done by using a fat32 partition with msdos io.sys and mbr. So the bootloader is dos. Grub4dos is loading an 80mb image into ram and booting that (win95 with ultrapack drivespace3). I'll confess some things not originally mentioned. I left them out, as to not confuse the situation. The device does have IDE and I can boot dos from that. However, as soon as any advanced OS attempts to boot from the IDE (the exception KolibiOS), the connection to IDE is lost. This is intentionally set in the bios by the manufacturer. Essentially the bios is marked as disabled. But it is a little more complex than that, and the details are in-depth. So I have syslinux chainload grub4dos or grub2. It is from the IDE that grub4dos loads the 80mb.img to ram. But if Win95 can in anyway see any partition, on the IDE, boot will fail. It does not matter what boot switches you use. And it does not matter if you are not even using the IDE. At some point Windows cannot access its own files and errors out, in some way or another. Or if booting from ram, and the partition is still visible, you end up with a protection error. The same is true trying safe mode, either way. That is why some very ambitious people wrote a coreboot bios replacement for the device. So the Win95 image needs to be in ram, and it needs to be mapped over the any IDE partition(s)[or mark them hidden]. I do believe that, eventually, I may find a way to get IDE access working. But only after working from inside Windows. And it will be a terrible hack, I am sure. Linux can boot from ram, but cannot see the IDE. You can edit the (Linux) ATA driver to use MSR configurations instead of PCI, and activate the MSRs related to IDE enabling. But using grub2 with the same MSRs modified (wrmsr) changes nothing for Win95. Windows uses the PCI configurations, so the MSR modifications hardly mean anything. Booting anything from USB can be rough. Some people have gotten certain sizes and manufacturers' pendrives to boot. While other do not boot at all. The USB booting issues arrive from the bootloaders hardly working at all, with this device. For me, dos boot over USB works every time; no matter what. In a few minutes I will try direct mapping the image from USB, booting from USB dos mbr, and directly running grub4dos (grub.exe) from the prompt. I may have tried that before, but actually can't remember for certain. The only problem is that USB is 1.1 speeds. For now that would work. I'm hoping this way just slipped my mind. Or that when I, possibly, tried it before, I hadn't learned that Windows would boot; if it can't access an IDE partition. I've been working on this for a long time. Masochist, I am. Anyway, this is a little bit more of a full disclosure. In the end, I intend to run from ram anyway. Drivespace is actually pretty cool, now. Back when 95 was new, I wouldn't have touched it with a ten foot pole. With faster memory and CPU, its kinda like Squashfs for Linux. If only there was something like Aufs for Win9x. Trying to set this mean device up, has taught me some neat things. For example, I learned how to modify Grub2 2.06 for Windows, to work from Dos. It needs to be chainloaded, but it is usable with just dos and Hxdos (no mbr install).

This is probably the least desired option, for most people. Mostly because it defeats the essence of escaping modern operating systems. But in a worst case senario, there is Dosbox. Now even for Win95 and Winnt. Maybe not an option for graphically hungry games. Note: The Dosbox version I am talking about is not an official build. So you can't download it from the Dosbox homepage.

The circumstances in this situation are far from typical. I get that I may already be dead in the water. First, the situation. This is a finished Win95osr2 install via Virtualbox. But now booting on a real machine. Grub4dos is being used, and direct mapping is not an option. So this is in memory (this is the only option for this device, unless fitted with a coreboot bios). So all detected devices are fine, until the final USB2 device. It hangs the system, before you can click cancel. Normally you could reboot into safe mode and, if present, disable it. But that won't work in this situation. I could also disable automatic device detection. But I need the other devices to be detected. So as soon as I detect them, the USB device will be detected with them. Once I can get a good boot, I can exit to Dos and save my work over USB. I have not been able to boot and run the image, direct mapping over usb, or I would be trying it that way first. Does anyone know if you can block detection of a device, via its bus:address; or something?