DC-SWAT Forum
Dreamshell 4 RC3 Bios Issue - Версия для печати

+- DC-SWAT Forum (http://www.dc-swat.ru/forum)
+-- Форум: Sega Dreamcast (/forum-2.html)
+--- Форум: English section (/forum-29.html)
+--- Тема: Dreamshell 4 RC3 Bios Issue (/thread-2238.html)

Страниц: 1 2


RE: Dreamshell 4 RC3 Bios Issue - Foxhound2153 - 16.02.2015 12:52

(16.02.2015 12:17)alex писал(а):  Wait.
What type of bios mod installed in your dreamcast, bios replacement or dual bios mod?
Can you make some pictures of your dreamcast, especially bios mod on motherboard

Maybe gamepad is not working, try with another one, try press A button instead START.

I think you may be right. I bet the problem lies with the region free bios mod. I need to check with the person who installed. I will say though that I see no switch so im guessing its not dual bios. I will try and find out more info and get back.


RE: Dreamshell 4 RC3 Bios Issue - BMan - 21.06.2015 08:04

Having the same issue. Can't figure it out. Foxhound2153, did you find an answer? Who installed you chip was it a service someone was selling on eBay?


RE: Dreamshell 4 RC3 Bios Issue - wilddingo - 11.03.2016 16:49

(11.03.2016 13:19)wilddingo писал(а):  same issue here.but finally I'v resolved it.please notice the text "can't read MBR".In fact,it's not MBR problem but the main partition table. I think you may done your SD card format by windows? The most of SD card I 'v
ever heard will be identified as a "removable device" under that circumstance, and windows treats all of such
things differrent from "fixed device".It doesnt create a partition table on it at all. The solution is using particular
software to create one then format that partion as a FAT32 fs. Or ,you can do that by using fdisk under Linux as I do. I think DreamShell's bootloader and core are both checking that partition table during boot process to determine where the target filesystem resides in. In this case,the last of 64 byte of the MBR will be something
other than the valid partition items so the partition parsing process goes wrong. Some historical versions may have differrent behaviour ,such as 4.0 beta4. It boots correctly without a valid partition table.