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/s...al/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 noct@noccy.com 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 noct@noccy.com 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.

[mon0]

Any news on that bug?

[DJ Egg]

I edited one of my posts above.
Not sure if it's relevant in your case though...

[mon0]

Originally posted by 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

Nope, i have the
keeponscreen=1 already, but it still crashes.

[DJ Egg]

Please post a StartUpList.
Maybe it's a conflict with some other concurrently running app?

Unzip & run StartUpList
and attach the results log to a new post here
(note: attachment feature is only available via "Post a Reply" button)

[mon0]

StartupList report, 03.01.04, 19:06:45
StartupList version: 1.52
Started from : I:\TEMP\STARTUPLIST.EXE
Detected: Windows 98 Gold (Win9x 4.10.1998)
Detected: Internet Explorer v6.00 SP1 (6.00.2800.1106)
* Using default options
==================================================

Running processes:

C:\WINDOWS\SYSTEM\KERNEL32.DLL
C:\WINDOWS\SYSTEM\MSGSRV32.EXE
C:\WINDOWS\SYSTEM\MPREXE.EXE
C:\WINDOWS\SYSTEM\ZONELABS\VSMON.EXE
C:\PROGRAMME\GEMEINSAME DATEIEN\SYMANTEC SHARED\CCSETMGR.EXE
C:\PROGRAMME\GEMEINSAME DATEIEN\SYMANTEC SHARED\CCEVTMGR.EXE
C:\PROGRAMME\CHERRY\CDI\CDI.EXE
C:\WINDOWS\SYSTEM\mmtask.tsk
C:\WINDOWS\EXPLORER.EXE
C:\WINDOWS\TASKMON.EXE
C:\WINDOWS\SYSTEM\SYSTRAY.EXE
C:\PROGRAMME\LOGITECH\MOUSEWARE\SYSTEM\EM_EXEC.EXE
C:\PROGRAMME\CREATIVE\SBLIVE\AUDIOHQ\AHQTB.EXE
C:\PROGRAMME\GEMEINSAME DATEIEN\SYMANTEC SHARED\CCAPP.EXE
C:\PROGRAMME\MOTHERBOARD MONITOR 5\MBM5.EXE
C:\PROGRAMME\ZONE LABS\ZONEALARM\ZLCLIENT.EXE
C:\PROGRAMME\CHERRY\KEYMAN\KEYMAN.EXE
C:\PROGRAMME\ACTIVE SMART\ACTIVESMART.EXE
C:\WINDOWS\SYSTEM\DDHELP.EXE
C:\WINDOWS\SYSTEM\RNAAPP.EXE
C:\WINDOWS\SYSTEM\TAPISRV.EXE
I:\PROGRAMME\MIRC\MIRC.EXE
C:\WINDOWS\SYSTEM\PSTORES.EXE
I:\PROGRAMME\MOZILLA\MOZILLA.EXE
I:\TEMP\STARTUPLIST.EXE

--------------------------------------------------

Listing of startup folders:

Shell folders Startup:
[C:\WINDOWS\Startmenü\Programme\Autostart]
Active SMART.lnk = C:\Programme\Active SMART\ActiveSMART.exe

--------------------------------------------------

Autorun entries from Registry:
HKLM\Software\Microsoft\Windows\CurrentVersion\Run

ScanRegistry = C:\WINDOWS\scanregw.exe /autorun
TaskMonitor = C:\WINDOWS\taskmon.exe
SystemTray = SysTray.Exe
LoadPowerProfile = Rundll32.exe powrprof.dll,LoadCurrentPwrScheme
EM_EXEC = C:\PROGRA~1\LOGITECH\MOUSEW~1\SYSTEM\EM_EXEC.EXE
AudioHQ = C:\PROGRAMME\CREATIVE\SBLIVE\AUDIOHQ\AHQTB.EXE
ccApp = "C:\Programme\Gemeinsame Dateien\Symantec Shared\ccApp.exe"
MBM 5 = "C:\PROGRAMME\MOTHERBOARD MONITOR 5\MBM5.EXE"
NvCplDaemon = RUNDLL32.EXE C:\WINDOWS\SYSTEM\NvCpl.dll,NvStartup
Zone Labs Client = C:\PROGRA~1\ZONELA~1\ZONEAL~1\zlclient.exe
CherryKeyman = "C:\Programme\Cherry\KeyMan\KeyMan.exe"

--------------------------------------------------

Autorun entries from Registry:
HKLM\Software\Microsoft\Windows\CurrentVersion\RunServices

TrueVector = C:\WINDOWS\SYSTEM\ZONELABS\VSMON.EXE -service
ScriptBlocking = "C:\Programme\Gemeinsame Dateien\Symantec Shared\Script Blocking\SBServ.exe" -reg
ccSetMgr = "C:\Programme\Gemeinsame Dateien\Symantec Shared\ccSetMgr.exe"
ccEvtMgr = "C:\Programme\Gemeinsame Dateien\Symantec Shared\ccEvtMgr.exe"
Cherry Device Interface = C:\PROGRAMME\CHERRY\CDI\CDI.EXE

--------------------------------------------------

Shell & screensaver key from C:\WINDOWS\SYSTEM.INI:

Shell=Explorer.exe
SCRNSAVE.EXE=
drivers=mmsystem.dll power.drv

--------------------------------------------------

C:\WINDOWS\WININIT.BAK listing:
(Created 31/12/2003, 1:28:58)

[rename]
NUL=C:\WINDOWS\TEMP\GLB1A2B.EXE

--------------------------------------------------

C:\AUTOEXEC.BAT listing:

C:\PROGRA~1\NORTON~3\NAVDX.EXE /startup
keyb gr,,C:\WINDOWS\COMMAND\keyboard.sys

--------------------------------------------------


Enumerating Browser Helper Objects:

(no name) - C:\PROGRAMME\FLASHGET\JCCATCH.DLL - {A5366673-E8CA-11D3-9CD9-0090271D075B}
NAV Helper - C:\Programme\Norton AntiVirus\NavShExt.dll - {BDF3E430-B101-42AD-A544-FADC6B084872}

--------------------------------------------------

Enumerating Download Program Files:

[CV3 Class]
InProcServer32 = C:\WINDOWS\SYSTEM\WUV3IS.DLL
CODEBASE = http://windowsupdate.microsoft.com/R...e/actsetup.cab

[Shockwave Flash Object]
InProcServer32 = C:\WINDOWS\SYSTEM\MACROMED\FLASH\FLASH.OCX
CODEBASE = http://download.macromedia.com/pub/s...sh/swflash.cab

[VivoActive Control]
InProcServer32 = C:\WINDOWS\DOWNLO~1\VVWEB.OCX
CODEBASE = http://www.vivo.com/ie/vvweb.cab

[Microsoft SS Outlook Control]
InProcServer32 = C:\WINDOWS\DOWNLOADED PROGRAM FILES\EXCIOL.OCX
CODEBASE = http://www.dlink.de/library/control/exciol.ocx

[Symantec RuFSI Registry Information Class]
InProcServer32 = C:\WINDOWS\DOWNLOADED PROGRAM FILES\RUFSI.DLL
CODEBASE = http://security2.norton.com/de/sa/co.../bin/cabsa.cab

[QuickTime Object]
InProcServer32 = C:\WINDOWS\SYSTEM\QTPLUGIN.OCX
CODEBASE = http://www.apple.com/qtactivex/qtplugin.cab

[WCGView Control]
InProcServer32 = C:\WINDOWS\DOWNLO~1\WCGVIEW.OCX
CODEBASE = http://www.worldcybergames.org/kr/gamewiz/WCGView.cab

[OPUCatalog Class]
InProcServer32 = C:\WINDOWS\SYSTEM\OPUC.DLL
CODEBASE = http://office.microsoft.com/ProductU...ntent/opuc.cab

[{E36C5562-C4E0-4220-BCB2-1C671E3A5916}]
CODEBASE = http://www.seagate.com/support/seato...npSeaTools.cab

[{CAFEEFAC-0014-0000-0001-ABCDEFFEDCBA}]

[InstallFromTheWeb ActiveX Control]
InProcServer32 = C:\WINDOWS\DOWNLOADED PROGRAM FILES\IFTW.DLL
CODEBASE = http://tw.msi.com*****autobios/client/iftwclix.cab

[Update Class]
InProcServer32 = C:\WINDOWS\SYSTEM\IUCTL.DLL
CODEBASE = http://v4.windowsupdate.microsoft.co...885.2051273148

--------------------------------------------------

Enumerating ShellServiceObjectDelayLoad items:

WebCheck: C:\WINDOWS\SYSTEM\WEBCHECK.DLL

--------------------------------------------------
End of report, 6.169 bytes
Report generated in 0,364 seconds

Command line options:
/verbose - to add additional info on each section
/complete - to include empty sections and unsuspicious data
/full - to include several rarely-important sections
/force9x - to include Win9x-only startups even if running on WinNT
/forcent - to include WinNT-only startups even if running on Win9x
/forceall - to include all Win9x and WinNT startups, regardless of platform
/history - to list version history only

[fraorlando]

Ok, here is my startuplist:

[Sledge]

Well, I've had the same problem with Duron750MHz and WinXPprofessional(!)

Everything started to work well when I put WA5 into a new directory not overwriting my old WA(2.92) UNLESS I've decided to bring back my old settings, thus I've copied Winamp.ini from an old WA to a WA5 dir.

WA5 crashed as soon as I've set skin to modern..

So the problem pinpoints to the only obsolete settings issue.

I attach the differences (in HTML) between a brand new installed WA5.ini and an old one

[mon0]

Originally posted by Sledge
Well, I've had the same problem with Duron750MHz and WinXPprofessional(!)

Everything started to work well when I put WA5 into a new directory not overwriting my old WA(2.92) UNLESS I've decided to bring back my old settings, thus I've copied Winamp.ini from an old WA to a WA5 dir.

WA5 crashed as soon as I've set skin to modern..

So the problem pinpoints to the only obsolete settings issue.

I attach the differences (in HTML) between a brand new installed WA5.ini and an old one

So, the essence of your message is, that when you did a clean install, it works for you?
Well i did that before, an absolutely clean install, but still a no go. Or did i get something wrong?

[Sledge]

Yes, I mean that. For my case it's a job to find the differencing line between those *.inis, but I'm just lazy to do that

Your problem is much more complex to scramble..

[mon0]

Any news on this issue?
WA 5.02 still gives me an error.

[Francis]

For those of you running litestep (or any other alternative shell), could you try killing it temporarilly, run the explorer shell and then try to run winamp5 again ? I don't know yet what is causing the bugs you describe, but I have a few ideas. Certainly, if something somewhere changed the USERDATA field of the various wa windows to the magic value that is used by litestep to keep windows in the active desktop, it would crash, because altho this wasn't used by winamp2 windows (classic skins), the field is used by freeform windows and should *not* be changed arbitrarilly (this is why freeform doesn't support the litestep option, though we might be able to devise something in the future).

Note that i'm not asking you to uninstall litestep, just disable it temporarily, and check if the error is associated with it.

To mon0, it seems you have a lot of plugins installed, could you try installing winamp in a new directory (do not forget to backup your current install!) and check wether a clean & *virgin* install still has the problem you describe ? If you don't get the problem, try moving the plugins over to the new install one by one and see when it starts puking. If you get the problem even with a virgin install, then it's something more obscure than just a conflict with an old plugin, and we'll have to look into it differently.

Thanks for your help guys!

Francis.

[mon0]

Originally posted by Francis
To mon0, it seems you have a lot of plugins installed, could you try installing winamp in a new directory (do not forget to backup your current install!) and check wether a clean & *virgin* install still has the problem you describe ? If you don't get the problem, try moving the plugins over to the new install one by one and see when it starts puking. If you get the problem even with a virgin install, then it's something more obscure than just a conflict with an old plugin, and we'll have to look into it differently.

Thanks for your help guys!

Francis. [/B]

Hi Francis,

the matter is, that i dont have a _single_ plugin - besides the delivered from Winamp itself - installed. As a stated above, i did a clean install a serveral times, with the same result.

[mark]

I use litestep and never had any issues like this. It could depend on the VWM module used.

ckVWM.dll works good for me

[mon0]

ello?
Any news guys?

[Dazog]

do u see this with 5.03?

[bandidu]

I've just tried with Winamp 5.03 and the same happened to me. Here are my computer details:

Windows 98
Internet Explorer 6.0 SP1
P IV 1.8 gHz
256MB RAM DDR

Here the error message (It's in portuguese, I hope you guys can understand):

WINAMP causou uma falha de página inválida no
módulo GEN_FF.DLL em 0167:01337b9e.
Registros:
EAX=0072ce38 CS=0167 EIP=01337b9e EFLGS=00210246
EBX=0072ce38 SS=016f ESP=0072cde8 EBP=0072cdfc
ECX=00000030 DS=016f ESI=00000000 FS=0f1f
EDX=00000000 ES=016f EDI=00000030 GS=0000
Bytes em CS:EIP:
39 77 10 75 21 39 77 0c 74 40 68 09 01 00 00 68
Esvaziamento da pilha:
00000000 00000030 0072ce38 00000030 00000030 0072ce54 013378d1 0072ce38 00000000 00000014 00000030 0072d36c 01337496 0072ce38 0072ce30 00000400

[mon0]

Originally posted by Dazog
do u see this with 5.03?

Yes.

[McLethal]

firstly, my specs:
winXP home, version 2002, SP1, running on 2.41GHz, 512MB RAM. I just cleanly installed winamp 5 (on administrator) account and it was running perfectly. No errors. Then I switched to a limited account, and it crashes instantly after running a song. I've tried the winamp5update, but nothing seems to work. any help is appreciated. thanks.

[DJ Egg]

Sorry, but you've posted in the wrong thread.
Your issue has nothing to do with the Win98FE modern skin issue reported by mon0.


Tech Support Forum
Sticky: Troubleshooters (read this first)

Limited Multi-User account issues
http://forums.winamp.com/showthread.php?threadid=161845
http://forums.winamp.com/showthread.php?threadid=163094

[3libras]

I "solved" it by loading another modern skin directly by double-clicking one of the .wal files...
Then went back to the skin I had and
everything works fine... (for now )

[bandidu]

I'd like to know if this issue was fixed on winamp 5.04. Anyone knows?

I have already sent a couple of e-mails about this bug, and I still didn't receive a single answer from winamp staff.

Regards,

[Omega X]

Ummm...


This issue pertains to Windows XP too. Though it only happens with newer modern skins. The skin loads then crashes Winamp.

AppName: winamp.exe AppVer: 5.0.0.4 ModName: gen_ff.dll
ModVer: 0.0.0.0 Offset: 00016329

WinXP Pro SP1
448MB
AMD Duron 700mhz
-------------------------
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 7/31/2004
Time: 8:23:25 PM
User: N/A
Description:
Faulting application winamp.exe, version 5.0.0.4, faulting module gen_ff.dll, version 0.0.0.0, fault address 0x00016329.

0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 77 69 6e ure win
0018: 61 6d 70 2e 65 78 65 20 amp.exe
0020: 35 2e 30 2e 30 2e 34 20 5.0.0.4
0028: 69 6e 20 67 65 6e 5f 66 in gen_f
0030: 66 2e 64 6c 6c 20 30 2e f.dll 0.
0038: 30 2e 30 2e 30 20 61 74 0.0.0 at
0040: 20 6f 66 66 73 65 74 20 offset
0048: 30 30 30 31 36 33 32 39 00016329
0050: 0d 0a ..
----------------------

[DJ Egg]

Which skins? Have you contacted the skin authors?
How do we reproduce the supposed bug?
I can't even reproduce it on Win98SE, let alone WinXP.

[Omega X]

Originally posted by DJ Egg
Which skins? Have you contacted the skin authors?
How do we reproduce the supposed bug?
I can't even reproduce it on Win98SE, let alone WinXP.

(I did all that and no cigar but...)

I think that I might know what the deal was. I fixed the problem myself by:

1) Navigate to the Plugins folder within the Winamp directory and Deleted all plugins MINUS the Visualization preset folders (AKA- "AVS" "MILKDROP" etc.)

2)Tossed out the Configurations .ini. in the WInamp root for safe measure.

3) Reinstalled Winamp.

After that, everything worked fine. Though I installed just about everything 1 plugin at a time just to see what the problem was.

I believe that it was an old NSF plugin that lets you listen to NES music files.(Might have been the reason for the new version I saw on Zophar.net)

This fix might not work for others but it worked for me...

[DJ Egg]

So basically, it's not reproducable under WinXP with a clean install of Winamp 5.04 or with just the default plugins present... in which case it's not Winamp bug.