WA5 crashes instantly when loading a modern Skin

[mon0]

Here we go.
Specs first:
Win98 First Edition
IE 6.0 SP1
SB Live Value
GF4 TI 4200 with Dets 53.04

I made an absolutely clean install of WA5. It starts normally with the Old Skin(s).
Then i tried to load a Modern Skin.
WA5 crashes instantly, with the follwing message:

WINAMP caused an exception error in Module GEN_FF.DLL at 0177:0124df07.

Register:
EAX=00000048 CS=0177 EIP=0124df07 EFLGS=00210206
EBX=00000000 SS=017f ESP=00645e70 EBP=00645e84
ECX=00641e78 DS=017f ESI=00000000 FS=7097
EDX=00000006 ES=017f EDI=030246e0 GS=0000
Bytes bei CS:EIP:
85 01 3d 00 10 00 00 73 ec 2b c8 8b c4 85 01 8b
Stapelwerte:
00645efc 011a7c25 00645f24 012852ae ffffffff 00645f30 011a7499 030246e0 00000000 030246bc 030247c0 00000000 00000000 ffffffeb 01ed3ce0 00000000

I searched the forum already and played arround with several options for the skins - no success.
It hangs up and crashes immediatly.
I dont know what i can do furthermore and hope, you can help me.


Number 2:

When i try to access the options of WA5 Modern Skins, i always get this message:

error parsing xml layer (tooltips-elements.xml).

xml processing instruction not at start of external entity of line 1.

But ONLY when i try to access the options the first time after i launched WA5 and only for the options of modern skins.

Cheers!

[DJ Egg]

hmm, Windows 95 and 98FE aren't really supported

You might need to install some updates.


[edit] suggested fix failed (i suck) [/edit]


You should go to Windows Update

http://v4.windowsupdate.microsoft.com/en/default.asp

http://www.microsoft.com/windows98/support/critical/default.asp

http://www.microsoft.com/windows98/

and make sure you have all major updates installed,
including any from the pc/motherboard manufacturer's site (eg. chipset drivers)


Let us know if anything helps...

[Useff]

I have had the same problem with Winamp 5, from the release clients up until the final build, and performing several clean installs did nothing for me. I'm a litestep user, and I ususally have the option "Always on Litestep Virtual Desktops" checked. Today, just to see what would happen, I unchecked the box. For some reason I was able to load a modern skin after I changed that particular option without Winamp crashing due to an error in gen_ff.dll.

Maybe you should try this.

[DJ Egg]

Yes, enabling the Litestep options in Winamp Prefs is also a known issue.

With Winamp closed, open winamp.ini (in Winamp dir) in Notepad,
and edit the following line accordingly:

keeponscreen=1

This will make sure both "Litestep VWM Compatible mode" and "Always on Litestep Virtual Desktops" are unchecked.

Note:
keeponscreen=2 enables "Litestep VWM mode"
keeponscreen=3 enables "Always on LVDs"
keeponscreen=4 enables both (however, this doesn't seem to be working, and the value is staying at "2", which could well be the cause of the problem?)

If I enable both options, then I also get the same error message (on winamp startup) as everyone else here...

WinXP version:

Winamp has encountered a problem and needs to close

AppName: winamp.exe | AppVer: 5.0.0.1 | ModName: gen_ff.dll | Offset: 00014c74


Update:
Note, this particular issue is fixed in Winamp 5.02
(Litestep options moved to Classic Skin prefs page)

[mon0]

I´ll try your tipps in the next days (busy with work atm).
Thanx anyway for your work to collect and post the links.

[lazerfisk]

I got the same problem...

Unhandled exception in Winamp.exe (GEN_FF.DLL): 0xC0000000F: Access Violation.

*sigh*

[mon0]

UPDATE:

Installed both XML-Packs, but still a no go. Same failure, same procedure.

Any Ideas?

Cheers.

[lazerfisk]

Okay... Listen up... I did a new clean install into c:\program\winamp5\ (instead of overwriting my old c:\program\winamp) and then the new skins worked. My guess is that it has to do with some of the plugins. Therefore, i'll post my plugins folder here. You people that has got problems with your WA5 and the new skins, match my list against yours and post what plugins we have in common, ok?

you can find me at noct(at)noccy.com (msn/e-mail)

---

2003-12-15 08:13 397 312 vis_avs.dll
2002-10-07 00:00 13 824 out_wave.dll
2001-12-30 16:08 15 360 out_disk.dll
2003-12-15 08:09 41 984 out_ds.dll
1999-01-05 01:30 17 408 out_cw.dll
1999-04-22 16:24 446 464 in_sid.dll
2002-09-01 01:10 31 232 in_wave.dll
2003-06-17 19:02 101 888 in_midi.dll
2003-03-23 09:42 130 560 in_mod.dll
2003-11-17 07:00 276 992 in_mp3.dll
1998-09-29 21:30 4 608 IN_TONE.DLL
2003-10-13 20:20 28 672 vis_nsfs.dll
2000-09-26 04:16 20 480 OUT_XF.DLL
2001-03-04 22:52 7 680 out_wm.dll
2003-04-15 22:06 54 272 in_wm.dll
1998-12-30 16:27 7 168 in_lrec.dll
2000-07-05 18:53 245 248 in_mjf.dll
1998-10-11 20:05 93 184 in_thx.dll
2001-07-19 01:36 20 480 out_mp3.dll
2002-07-21 07:46 84 480 read_file.dll
2001-08-05 22:55 713 728 gen_rctl.dll
2003-11-13 21:52 11 264 GEN_TRAY.DLL
2002-12-16 21:04 147 456 dsp_mfx2.dll
2001-04-05 17:56 32 768 dsp_tom.dll
2002-12-16 22:23 77 824 dsp_wd.dll
2002-12-16 22:23 151 552 dsp_ady.dll
2002-03-31 18:48 257 536 out_sqr.dll
2002-07-20 01:42 15 872 gen_mircex.dll
2002-12-16 22:23 14 848 dsp_compwide.dll
2002-12-16 22:23 84 992 dsp_dceq.dll
2002-12-16 22:23 62 976 dsp_DeFX.dll
2002-12-16 22:24 172 032 dsp_enh.dll
2001-09-20 17:16 129 536 dsp_tool.dll
2002-12-20 02:52 237 568 gen_dosomething.dll
2001-10-29 06:31 126 976 dsp_sc.dll
2000-09-26 04:16 20 480 out_null.dll
2003-11-17 06:59 70 144 in_cdda.dll
1999-02-22 13:34 143 360 BUZZPLAY.DLL
1998-05-09 00:48 27 648 DSPLIB.DLL
2003-06-15 22:13 226 816 in_vorbis.dll
2001-08-03 01:11 270 336 lamedll.dll
2003-04-24 07:09 208 896 CDDBUIWinamp.dll
2003-04-24 07:09 212 992 CDDBControlWinamp.dll
2001-10-15 04:04 19 968 in_line.dll
2001-10-15 04:06 36 864 in_aupec2.dll
2001-10-15 04:06 69 632 in_MAC.dll
2001-10-15 04:06 40 960 in_umx.dll
2001-10-15 04:25 20 480 in_noise.dll
2001-10-31 10:44 65 536 in_BuzzWinAmpBridge.dll
2002-04-10 04:32 12 800 out_dswocf.dll
2003-12-13 22:31 176 640 in_nsv.dll
2003-11-26 10:55 66 560 nsvdec_vp5.dll
2003-11-17 07:03 63 488 in_dshow.dll
2003-04-15 22:03 139 264 nsvdec_aac.dll
2002-12-14 23:53 221 184 dsp_oddcast.dll
2003-11-14 09:18 421 888 vis_milk.dll
2002-01-15 07:06 220 672 Vis_LIS104.dll
2003-06-14 06:42 264 192 gen_lucidamp3.dll
2003-07-24 15:43 110 592 gen_scripting.dll
2002-08-05 18:36 466 944 in_jline.dll
2001-05-22 01:59 4 153 344 dsp_iZVinyl.dll
2003-10-25 18:41 610 816 vis_glide_quarkamp.dll
2003-10-25 18:52 319 540 vis_geis.dll
1997-10-23 08:47 227 840 VIS_MUX.DLL
2003-11-02 00:05 286 720 gen_irc.dll
2003-10-22 06:33 204 800 enc_aac.dll
2003-12-15 21:20 24 576 enc_lame.dll
2001-12-21 07:48 135 168 lame_enc.dll
2003-10-11 19:52 49 152 vms_desktop.dll
2003-11-29 08:45 16 896 gen_hotkeys.dll
2002-01-15 07:07 162 816 Vis_LIS104RIP.dll
2003-11-26 10:57 68 096 nsvdec_vp6.dll
2003-12-15 11:58 89 600 dsp_sps.dll
2003-12-16 09:33 355 840 gen_ml.dll
2003-12-16 08:17 2 150 912 gen_ff.dll

[fraorlando]

I ve got the same problem here, with similar system specs.(xp2400+,win98se,sp1) Tried updating xml and everything as DJ Egg proposed,but it still doesnt work. Interestingly, the beta 2 worked with modern skin (though there was the xml parsing error at startup)

[DJ Egg]

*bump*

Treat as Top Priority





______________________________________________________

General Reminder:

Please people, include all relevant system specs as outlined in the 2 stickys:
Post all Winamp 5.0F Bugs here
How to write a useful bug report



@lazerfisk

We do not support 3rd-party plugins in the Bug Reports forum.
We only support clean installs with NO 3rd-party plugins.
If your problem was caused by a 3rd-party plugin, then alas, it is not our problem.
Thankfully, you managed to solve yours, or so it would seem....

However, discussion about these 3rd-party plugins will not continue here.
Take it to Tech Support or Winamp Discussion forum instead, if you must.

Thank you.



Note:

@all

A clean install means you uninstall previous versions, delete the Winamp folder,
then install Winamp.
If you need to backup anything first, instructions are here

ps. If you installed to the same dir where Winamp3 previously resided
then this will be the cause of the problem.
Winamp 5.0 is the upgrade from Winamp 2.x
Winamp3 was a separate product entirely.
So if there was any wasabi related files already in the dir
(eg. studio.xnf config file)
then this will certainly cause a conflict.

Sure, this might not apply to everyone who has posted in this thread,
but I'm just covering bases for now,
until the devs can get to the bottom of this...

[mon0]

Originally posted by DJ Egg
Note:

@all

A clean install means you uninstall previous versions, delete the Winamp folder,
then install Winamp.
If you need to backup anything first, instructions are here

ps. If you installed to the same dir where Winamp3 previously resided
then this will be the cause of the problem.
Winamp 5.0 is the direct upgrade from Winamp 2.x
Winamp3 was a separate product entirely.
So if there was any wasabi related files already in the dir
(eg. studio.xnf config file)
then this will certainly cause a conflict.

Sure, this might not apply to everyone who has posted in this thread,
but I'm just covering bases for now,
until the devs can get to the bottom of this...

Well, i used Winamp 2.91 before IIRC. But i deleted everything with Winamp-Content (folders and registry).

[mon0]

To keep you updated:

WA 5.01 doenst change everything on that problem.

Cheers.

[Dazog]

Stickied.

Until we solve it.

[lazerfisk]

Dj Egg, my bug-report had nothing to do with support of third-party plugins. It was merely an attempt from my side to help resolve an error that seem to be quite common. If WinAmp 5 crashes if a thirt-party plugin is present and people complain about this, it should be in the interest of the users to know which plugin is faulty. I understand that you don't think this is a WinAmp5 bug-report, but it is WinAmp5 that crashes, and not the third-party plugin

Sorry if i stepped on any toes with my last post. And if anyone browsing this thread is interested in resolving this problem without doing a clean install and having to re-install all your plugins, drop me a mail at [email protected] with a list of your plugin folder contents.

Best regards,
Christopher

[Dazog]

Originally posted by lazerfisk
Dj Egg, my bug-report had nothing to do with support of third-party plugins. It was merely an attempt from my side to help resolve an error that seem to be quite common. If WinAmp 5 crashes if a thirt-party plugin is present and people complain about this, it should be in the interest of the users to know which plugin is faulty. I understand that you don't think this is a WinAmp5 bug-report, but it is WinAmp5 that crashes, and not the third-party plugin

Sorry if i stepped on any toes with my last post. And if anyone browsing this thread is interested in resolving this problem without doing a clean install and having to re-install all your plugins, drop me a mail at [email protected] with a list of your plugin folder contents.

Best regards,
Christopher

Its not.

If you open a plugin not shipped with winamp and ANYTHING crashes its the plugin.

NOT winamp

THE plugin caused winamp to Crash, since its probably not written and/or updated to work with winamp 5.

Therefore we would point you to email the plugin maker and request them to update and or fix the problem.

Soon Sdk's will be released for people to do so easily.

So its not a Winamp bug, but a third party problem.