Published on March 13, 2004 By Ande In WinCustomize Talk
I’ve been using Boot Skins for a short period of time without any problems. I have noticed recently during the boot up sequence of the computer (just prior to the boot screen showing) a message at the top of the black screen: -
“INVALID BOOT.INI FILE
BOOTING FROM C:\WINDOWS”

I contacted Stardock who advised me that boot skins has nothing to do with the boot.ini file

I have attempted to edit the boot.ini file through the “System Startup”- “edit” - and get the message: -
“Cannot locate the c:\ boot.ini file, do you want to create a new file.”

Stardock did ask me if I had used any other programs to alter boot skins (I have not).

I have uninstalled Boot Skins – rebooted- Message still present. Reinstalled - -rebooted – Message still there. I would like to get my computer back to square one. Can anyone assist?



Comments (Page 3)
4 Pages1 2 3 4 
on Mar 16, 2004
John,Gary I'm back sort of. Any problems I've had are all of my own making I think. I've spoken to Jafo on the phone (He's just down the track) and I think he is still ROFLLL.
I did what John said and it worked like a charm, the boot.ini was back. I said to myself, what a smart little guy you are. So I clicked "apply" (should I have?) rebooted and I was locked out completly. After that, everything is a blur. I have no real recollection of what actually occurred. I have vague pictures of floppy boot disks, XP install CD, boot CD. By the time the smoke cleared (comming out of the nostrils) the scene wasn't very pretty. No matter what I did I could not get back in.

To cut along story short, I took the ##''## computer down too the local Comp. Shop.
And do you know what - they laughed at me?. After they picked themselves up off the floor, they assured me they would fix everything up. I said don't - just format both drives - load XP again and give me the ##''## back. It's been a couple of years and the puter needed a good clean out. So i'm sitting here loading everything back on. isn't it great I had backed everything up.

on Mar 16, 2004
Jafo promises to cease laughing.....eventually....honest...
on Mar 16, 2004
Your Security Index Logs where over filled ?

I know that a lot of people end up formattig after finding that they can not log in and the computer seems to have forgotten their password and it turns out that the Security Logs are to large. So you have to boot into safe mode as Admin, flush the log/index and reboot, everything should be ok fine upon reboot...

mmm

dunno, good to hear it is back online thought !!

Hey, with Paul that close you should have grabbed a suitcase (24 pack of brew) and heading over with the computer

ahhh, well, maybe a 6 to start and once ok fine a few more if I remember corretly working on computers hald blind was always a bad idea hind sight

on Mar 16, 2004
I work better totally sozzled...
on Mar 16, 2004
...pass the Coopers

...it's always nice when you can give the gift of laughter to so many

Glad it's up



Powered by SkinBrowser!
on Mar 16, 2004
I thought that one time and when I went to boot up after stuffing the cables and everything into this micro-mini tower and the system wouldn't boot. So I pulled it apart and looked everything over (so I thought) and found all was fine, turned it on and nothing, looked at the PSU and found the fan was dead... so I quit for the night fully knowing I needed a new PSU even though it was a new case. The next day I pulled one out and sat it on the bench, started pulling cables and cards and got down to where I could see the (P1-P2) power feeds to the momboard...

I didn't have to disconnect them
on Mar 16, 2004
Glad it's up


ahhh

China going to jump all over that
on Mar 17, 2004




Powered by SkinBrowser!
on Mar 17, 2004
-r -a -s -h




Sorry, I couldn't resist... The problem is solved other than the pesky itching...
on Mar 17, 2004
lol, well, hives probably could be a side affect no doubt
on Mar 17, 2004
I have attempted to edit the boot.ini file through the “System Startup”- “edit” - and get the message: -“Cannot locate the c:\ boot.ini file, do you want to create a new file.”


Clearly, you need to create a new one. So, you probably should answer yes. I remember that BootXP messed with that file. It probably wasn't properly restored.

The new file should look like the information in #6 and #7. If not then copy it into the new blank file.

If no file was created, then you can create a txt file using notepad in the C:\ root directory. Put into it the information in #7(no spaces) and save it as boot.txt Then, open the c directory and rename it to boot.ini This should solve the issue.
on Mar 17, 2004
ahhh

nevermind..
on Mar 17, 2004
Now how did I miss #37?
on Mar 17, 2004
Better late then never...

.......it is still up tho



Powered by SkinBrowser!
on Mar 17, 2004
Down Boy, Down!
4 Pages1 2 3 4