Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Solved - Custom bootable skins Crash!  (Read 1395 times)

0 Members and 1 Guest are viewing this topic.

Ummon

  • Trade Count: (+13)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 5244
  • Last login:June 09, 2010, 06:37:18 pm
Solved - Custom bootable skins Crash!
« on: February 05, 2008, 10:21:49 pm »
Going from this thread, I decided to make my own boot skin in Paint that was just a black screen. After editing the startup options and restarting, my drive won't boot. It just doesn't do anything after the card and motherboard bios screens. Does anyone have any idea what I can do to fix this? Thanks.
« Last Edit: February 06, 2008, 05:16:19 pm by Ummon »
Yo. Chocolate.


"Theoretical physics has been the most successful and cost-effective in all of science."

Stephen Hawking


People often confuse expressed observations with complaint, ridicule, or - even worse - self-pity.

Kangum

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 461
  • Last login:February 25, 2018, 07:46:20 am
Re: Custom bootable skins Crash!
« Reply #1 on: February 05, 2008, 11:11:56 pm »
go into safe mode and undo it.

(press F8 key during boot)
« Last Edit: February 05, 2008, 11:16:06 pm by Kangum »

Ummon

  • Trade Count: (+13)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 5244
  • Last login:June 09, 2010, 06:37:18 pm
Re: Custom bootable skins Crash!
« Reply #2 on: February 05, 2008, 11:36:29 pm »
When I press F8 it doesn't go into safe mode but instead gives me this little blue dos-like menu with the list of drives available. If I select the hard drive it goes back into its stall mode. Blank screen at 640x480. Hmmm. The image was 640x480. Maybe it's stuck on that image. No idea how to get to it, though.
Yo. Chocolate.


"Theoretical physics has been the most successful and cost-effective in all of science."

Stephen Hawking


People often confuse expressed observations with complaint, ridicule, or - even worse - self-pity.

clickhea

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 418
  • Last login:August 09, 2019, 07:33:40 am
Re: Custom bootable skins Crash!
« Reply #3 on: February 06, 2008, 12:08:16 am »
thats because your in the bios

protokatie

  • I DO try to be insulting and horrible to my fellow Terran
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1396
  • Last login:March 27, 2012, 09:36:43 pm
  • Is anyone here a member of team retard?
Re: Custom bootable skins Crash!
« Reply #4 on: February 06, 2008, 12:09:03 am »
Depending on what version of Windows you are using and what vendor your BIOS is, it isnt always F8 that brings up the menu. Try holding down CTRL or even F10. Check with your compies docs to see what button brings up the proper menu. (On my computer, I believe it is F2 of all things...)
--- Yes I AM doing this on purpose, and yes I DO realize it is pissing you off.

---If my computers were cats, my place would look like an old widows house, with half of the cats having obvious health problems

Kangum

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 461
  • Last login:February 25, 2018, 07:46:20 am
Re: Custom bootable skins Crash!
« Reply #5 on: February 06, 2008, 01:08:19 am »
i actually googled before i posted that because i thought it was F5 and it microsoft support site stated for windows xp its F8. thats why my post had the edit because i googled it first. so much for microsoft support.

like protokatie said apparently you will have to look it up wich F key it is for your particular machine.

protokatie

  • I DO try to be insulting and horrible to my fellow Terran
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1396
  • Last login:March 27, 2012, 09:36:43 pm
  • Is anyone here a member of team retard?
Re: Custom bootable skins Crash!
« Reply #6 on: February 06, 2008, 03:04:19 am »
Quote
If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.


This is a quote from Vista help. But still may not work for XP or Vista people. It WOULD be nice if they made this a universal thing, as opposed to it being different for almost all models/OS's... :(

EDIT: Addition! DL Knoppix onto a CD or DVD and boot with that, then delete the file you mangled. (Dont know why I didnt think to add this before.) Knoppix,, in case you didnt know is a freely available Linux/Xwin distro based on Debian, that can load without being installed. Do not try to save files to an NTFS disc tho, as the NTFS drivers for KNOPPIX could corrupt data. You can still delete the bad .BMP file tho. And thus restore things to their origonal state.
« Last Edit: February 06, 2008, 03:13:35 am by protokatie »
--- Yes I AM doing this on purpose, and yes I DO realize it is pissing you off.

---If my computers were cats, my place would look like an old widows house, with half of the cats having obvious health problems

Ummon

  • Trade Count: (+13)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 5244
  • Last login:June 09, 2010, 06:37:18 pm
Re: Custom bootable skins Crash!
« Reply #7 on: February 06, 2008, 05:06:13 pm »
Okay. I got it. A friend told me to use my XP disc to do a repair. There were some errors but that didn't fix it. Then I  thought, 'wait, I'm at the command line....perhaps if I just delete the boot.bmp, it'll be fine.' And it was. Boots up now. Thank you for the support.
Yo. Chocolate.


"Theoretical physics has been the most successful and cost-effective in all of science."

Stephen Hawking


People often confuse expressed observations with complaint, ridicule, or - even worse - self-pity.

FhM

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 71
  • Last login:February 26, 2018, 03:33:01 pm
Re: Solved - Custom bootable skins Crash!
« Reply #8 on: February 06, 2008, 06:10:42 pm »
I have had more luck doing this kind of thing with a  program called bootskin. It gives you exact instructions of how to fix it if it goes wrong as well.

TheShanMan

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1912
  • Last login:October 22, 2024, 11:51:12 am
    • My Arcade (updated 1/30/13)
Re: Solved - Custom bootable skins Crash!
« Reply #9 on: February 06, 2008, 06:53:49 pm »
Yeah, bootskin is great. I have a centipede cab that's in great shape, so rather than giving it a mame theme, I wanted to stick with a centipede theme. I used the centipede arcade flyer for the BIOS screen, the windows boot screen, and the windows wallpaper. Plus some centipede wav's for startup and shutdown. Bootskin was easy to use, and making a bootskin file is easy too. It's just a zip file with a .bootskin extension.
My Collection: Mame cab, 38 dedicated vids, pin, skeeball, coin op air hockey table, Ice Cold Beer, Megatouch, 2 token machines, and payphone (VAPS, pics at Arcade Crusade)

Add Ambience to your mame cab setup

Ummon

  • Trade Count: (+13)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 5244
  • Last login:June 09, 2010, 06:37:18 pm
Re: Solved - Custom bootable skins Crash!
« Reply #10 on: February 09, 2008, 11:50:03 pm »
Thanks. I forgot I have that laying around.
Yo. Chocolate.


"Theoretical physics has been the most successful and cost-effective in all of science."

Stephen Hawking


People often confuse expressed observations with complaint, ridicule, or - even worse - self-pity.