It wrecked my win 2k box
#1
Posted 10 April 2003 - 07:38 AM
I then started in safe mode and tried to uninstall but I get an installer error. I figure - maybe I need to install the new win installer that I got from the link to microsoft. Well -- that didn't work -- I get another error -- can't install from safe mode. Yes -- Nero and In-CD are installed but I can't uninstall them either -- same error.
I'm screwed and I'm gettin pissed off. Thanks to this trial version I'll probably have to strip the drive (80 gig) and reinstall everything. What an incredible waste of time! After finding my way to this forum on my other system I notice that there are "a lot" of posts concerning problems with this program. If I can get it off my drive I'll never want to have anything to do with it again -------- EVER. It's been a long time since I've seen something this buggy. Do people actually pay for this?
#2
Posted 10 April 2003 - 08:35 AM
Example: Easy CD Creator - Including DirectCD = total useless piece of junk software; Same with InCD from Nero
What is the use of packet writing software? its faster to bring up Nero Burning Rom and burn the files you want on it.
3 Computers all running Alcohol very well all have Windows 2000 Pro/Server
Have fun!!
#3
Posted 10 April 2003 - 09:19 AM
Why not if it was working fine before he installed it, and then after alcohol was installed he got his blue screen, why can't he? It does happen.....
It would have been better if you put the error in your post, but since you didn't it would be a shot in the dark, have you tried using the repair console? try a registry scan from the repair console first.
Edited by tenndevil, 10 April 2003 - 09:23 AM.
#4
Posted 10 April 2003 - 11:16 AM
You don't say where you downloaded the version you are using from??? if it was not from our main download and sales site then there is a big risk that it was corrupt in some way,
We will be releasing a new version today, i suggest you re start your PC on safe mode and remove all Alcohol entrys in your "reg" Then download and the newest version from our download site at www.alcohol-software.com and re install... this should then solve your problem.
#5
Posted 10 April 2003 - 11:21 AM
Use the Recovery Console...
offtopic...
Is there a changelog or features list available?
#6
Posted 10 April 2003 - 12:47 PM
Is there a changelog or features list available?
Always
http://forum.alcohol...=ST&f=10&t=3255
#7
Posted 10 April 2003 - 10:40 PM
Use the Recovery Console...
offtopic...
Is there a changelog or features list available?
...and how EXACTLY does one 'repair' the computer using the recovery console?
Reason I ask is, that I recently did a motherboard / CPU upgrade, and my dual-boot Win XP/98 refused to boot into XP at all leaving me two options.
One: try and 'repair' by re-installing! (CD option; not exactly very helpful!)
Two: use the recovery console.
Having subsequently looked on the MS web site about the recovery console info, it seems you have to be an 'expert user' and versed in CLI commands.
Pretty unrealistic really don't you think?
(BTW, Win 98 booted fine, and after an Intel chipset .inf update, worked as previously).
Lazer.
Edited by Lazer, 10 April 2003 - 10:47 PM.
#8
Posted 10 April 2003 - 11:08 PM
#9
Posted 10 April 2003 - 11:16 PM
So if Alcohol screws up your OS, (as the original poster said) you have to ask MS for the solution?!
LOL
Some 'support'!
Lazer.
#10
Posted 10 April 2003 - 11:39 PM
LOL
Some 'support'!
Lazer.
Alcohol has been tested in many systems and MS operating systems, and it does not "screws" the operating system. The problem is that sometimes other software creates conflicts with Alcohol.
#11
Posted 11 April 2003 - 12:25 AM
It also doesn't help that you don't post again. If you want to fix your problem, run recovery console and type these commands and hit enter each time:
C:
cdwindowssystem32drivers
copy ax*.* ax*.*.bak
del ax*.*
Then reboot and all should be well.
#12
Posted 11 April 2003 - 12:37 AM
There's no bug free software, and Alcohol is not exception. But I can guarantee you that there are many registered and satisfied users. As you can't complete the installation, don't you think it's a bit premature blaming Alcohol?
#13
Posted 11 April 2003 - 12:38 AM
sorry to hear it, but if the windows installer (MSI) is giving a error on install (for msi installation itself ), theres little anyone here can do to help...
what was the service pack prior to the install of a120%...???
>>Theory one:::
alcohol 120 is very stable, but it is kernal heavy (my opinion mind you). if there are other programs that have loaded kernal level apps such as the mentioned packet writting, direct cd, antivirus, scsi drivers and other burning software, you can overun the stack. this results in a blue screen, things like "driver not equal" "overflow" mesages and lots of other nick nacks like that on the blue screen of pain.
the problem is that even if you uninstall most of these apps they leave thier .sys kernal drivers in place, and the still occupy stack space, hence you load alcohol and it comes crashing down.
>>theory two:::
this is a upgraded OS, which MSI 2.0 is known to not work with well. as it has to migrate the whole shebang from a previous os to a new os....then upgrade via service pack or program to MSI 2.0 (or 2.01) and it eats itself and dies... (this is very common for me to hear as i do corporate AV support, boy do they love upgrading)
>>theroy three:::
it was a perfectly happy and healthy OS and upgrading to msi 2.0 killed it. this is also failry common theme on my phone.
summary on theories:
1-the previous burning apps loaded the kenral's back and a120 pushed it beyond the limits. like a 20000lbs truck on a 10000lbs bridge
2-upgrade is convenient, but not even microsoft reccomends upgrading and will not support our clients who do so. in the end upgrading is not that great and causes unseen issues later
3-msi sucks. the world hates it. i hate it, my users hate it, and my customers hate it. for a short period of time msi 2.0 wasnt going to be included in sp3 because of this very issue.
sadely, a120 is *NOT* the cause of this failure...its all about msi.
im afraid after re-reading the opening dialoge i can only say that its is likey installing a120% killed the system..***BUT*** its not the a120% program thats at fault, its msi....
im not on the a120% staff, but i do fell the need to defend a120% because i see and hear these things 2-3x a day in my support work here at symantec.
msi does cause this, and it sucks. on a fesh system if you install a120% im sure it would work fine...(note: im not saying you need a fresh os to use a120%)
*enviorment is critical to any application thats loading a realmode driver.*
i wish i had help for you but i dont..
you will likely need to reformat and restore your system from your most recent backup.
there is this link here i found, but its not for the faint....use at your own risk
http://appdeploy.com...emove_msi.html).
Maxx
Edited by maxxcool, 11 April 2003 - 12:43 AM.
#14
Posted 11 April 2003 - 12:49 AM
nice one andareed ...didnt even cross my mind to delete the vitual drive
Maxx
#15
Posted 11 April 2003 - 12:50 AM
this is not a windows support forum, please keep your comments constructive or dont post. negativity will not help this gentleman.
Maxx
Edited by maxxcool, 11 April 2003 - 12:51 AM.
#16
Posted 11 April 2003 - 01:10 AM
As for the virtual drive installation, most of the installation is handled through dll's and not the msi itself, so it is probably not the msi's fault (but it could be).
Also, the link you posted is malformed and has a ')' at the end.
#17
Posted 11 April 2003 - 01:22 AM
#18
Posted 11 April 2003 - 01:33 AM
lets try that link again....
http://appdeploy.com...remove_msi.html
there wasnt supoosed to be a ) .... i grabbed it from the dbase by accident...
i get too many calls on a msi rollout (sms/kickstrart) failing and doing some nasty stuff to windows to dismiss msi's ability to mis-register dlls and do damage...youre a helluva programmer so ill differ to your opinion.....
(i just cant get over the feeling msi is involved in this failure though)
Maxx
#19
Posted 11 April 2003 - 06:48 AM
All's well in mudville -------- I got it to uninstall --- just had to be quick with the mouse and get to control panel before the demons woke up.
It probably had more to do with In-CD and Nero than anything else. Will anything co-habitate with Nero?
Sorry to come off like such a grump -- but I do get so weary of going through these Windows brain teaser exercises. After all -- I bought the computer with the idea of actually using it. It's supposed to be a video editing box.
If I dump Nero and his friends I suppose I can get Alcohol to run. Like I said -- the install went OK -- but when I rebooted -- that's when the fun began. I've been through this type of thing a few times before -- but I've yet to enjoy it.
Note to ---- Maxxcool -- It's SP3, not a 2k upgrade and I never installed MSI. It all runs on an IDE RAID (pair of 40's) which has a bit to do with the joy I felt at the prospect of having to bring it up from zero.
Thanks for the help just the same.
#20
Posted 11 April 2003 - 06:54 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users