• Registered: 2006-07-24
  • Posts: 18

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

@RogueSpear - Definitely as an admin.  I only create one user at the prompt for creating users (I don't do full unattended) called 'Admin' and it's automatically assigned admin rights by the XP installer.

@Bâshrat -  I realize it does not give you any more detailed information but it's also clear that it's not an issue with the install routine executing at first login.   I was worried that the nlite/ryanvm integration might be screwing it up and I was hoping I could end up with an Bâshrat the Sneaky integrated XP installation that I could clone to other systems.  What can we do to get you usable info?  The 'debug option' is not working.  Should I make my ISO or the resulting installed VMware image available to you for analysis?  I could provide you with remote access to the running VMware image via a VNC session where you could take a look at the resulting install and the CD image.  I could also dump a copy of the folder that I have the BASE and packs setup into the VMware image.

-felipe

  • From: Amherst, NY
  • Registered: 2006-05-27
  • Posts: 271

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

@Bâshrat the Sneaky, the error "Cannot delete element from array" is probably an error that, if it were visible, would give some more useful information that could be captured in a screenshot.  Would it be possible to have the "debug" option halt execution and show the actual error dialog?

RogueSpear's Website

  • [dk]
  • DriverPacks Magician
  • Offline
  • Registered: 2006-09-05
  • Posts: 44

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

@Bâshrat the Sneaky - so you need any extra information I could provide?
And another question - could finisher be executed via cmdlines.txt before MUI is integrated?
(to get rid of possible conflicts with locale), although I've got following strings in winnt.sif:

[RegionalSettings]
    LanguageGroup=5,1
    SystemLocale=00000419
    UserLocale=00000419
    InputLocale=0409:00000409,0419:00000419

Last edited by [dk] (2006-09-27 17:06:22)

Mars 2025 - Online military-economic strategy game.

[dk]'s Website

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

@all: debug mode should be working, I've used it before to debug the exceptions and KTD functionality. There must be one tiny typo or something that prevents the debug statements that I've added from working.

@RogueSpear: no, THAT is the error: that an element could not be deleted from an array. Probably because an incorrect index is specified, but that's the reason for adding all those debug statements, but unfortunately they're simply not working...

@[dk]: I'm now confident that it has absolutely nothing to do with the system's locale. Don't waste your time on that. But as you can see, it only happens on a very small amount of systems. So it's got to be something tiny...

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • fejker
  • DriverPacks newbie
  • Offline
  • From: Croatia
  • Registered: 2006-09-27
  • Posts: 3

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

I'm encountering the same error, too!


Code:

2006-09-27 13:11:14 : <INIT> DriverPacks Finisher 6.08.6 initialized.
2006-09-27 13:11:14 : <INIT> Detected platform wnt5_x86-32.
2006-09-27 13:11:14 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-09-27 13:11:14 : <INIT> 1. ACPI devices

ACPI\AUTHENTICAMD_-_X86_FAMILY_6_MODEL_10\_0                : AMD Athlon(TM) XP 2500+
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\PNP0000\4&10C7922&0                                    : Programmable interrupt controller
ACPI\PNP0100\4&10C7922&0                                    : System timer
ACPI\PNP0200\4&10C7922&0                                    : Direct memory access controller
ACPI\PNP0303\4&10C7922&0                                    : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0700\4&10C7922&0                                    : Standard floppy disk controller
ACPI\PNP0800\4&10C7922&0                                    : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&10C7922&0                                    : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\3                                              : Motherboard resources
ACPI\PNP0C02\4                                              : Motherboard resources
ACPI\PNP0C04\4&10C7922&0                                    : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Uniprocessor PC
18 matching device(s) found.

2006-09-27 13:11:14 : <INIT> 2. PCI devices

PCI\VEN_1002&DEV_4E48&SUBSYS_4E481FD3&REV_00\4&1FEB96E4&0&0008: RADEON 9800 PRO (Microsoft Corporation)
PCI\VEN_1002&DEV_4E68&SUBSYS_4E491FD3&REV_00\4&1FEB96E4&0&0108: RADEON 9800 PRO SEC (Microsoft Corporation)
PCI\VEN_1106&DEV_0571&SUBSYS_80ED1043&REV_06\3&61AAA01&0&79 : VIA Bus Master IDE Controller
PCI\VEN_1106&DEV_3038&SUBSYS_80ED1043&REV_81\3&61AAA01&0&80 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_80ED1043&REV_81\3&61AAA01&0&81 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_80ED1043&REV_81\3&61AAA01&0&82 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3038&SUBSYS_80ED1043&REV_81\3&61AAA01&0&83 : VIA Rev 5 or later USB Universal Host Controller
PCI\VEN_1106&DEV_3059&SUBSYS_810D1043&REV_60\3&61AAA01&0&8D : Multimedia Audio Controller
PCI\VEN_1106&DEV_3065&SUBSYS_80ED1043&REV_78\3&61AAA01&0&90 : VIA Rhine II Fast Ethernet Adapter
PCI\VEN_1106&DEV_3104&SUBSYS_80ED1043&REV_86\3&61AAA01&0&84 : VIA USB Enhanced Host Controller
PCI\VEN_1106&DEV_3149&SUBSYS_80ED1043&REV_80\3&61AAA01&0&78 : VIA SATA RAID Controller
PCI\VEN_1106&DEV_3189&SUBSYS_00000000&REV_80\3&61AAA01&0&00 : VIA Standard Host Bridge
PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&61AAA01&0&88 : PCI standard ISA bridge
PCI\VEN_1106&DEV_B198&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : VIA CPU to AGP Controller
PCI\VEN_1131&DEV_7130&SUBSYS_00001131&REV_01\3&61AAA01&0&98 : Multimedia Controller
PCI\VEN_1397&DEV_2BD0&SUBSYS_2BD01397&REV_02\3&61AAA01&0&58 : Network Controller
16 matching device(s) found.

2006-09-27 13:11:14 : <INIT> 3. HDAUDIO devices

No matching devices found.

2006-09-27 13:11:14 : <INIT> 4. USB devices

USB\ROOT_HUB\4&1A929F47&0                                   : USB Root Hub
USB\ROOT_HUB\4&1D9A72A8&0                                   : USB Root Hub
USB\ROOT_HUB\4&7D8EEA2&0                                    : USB Root Hub
USB\ROOT_HUB\4&AE0C203&0                                    : USB Root Hub
USB\ROOT_HUB20\4&13F2BADF&0                                 : USB Root Hub
USB\VID_046D&PID_C501\5&4D81C3A&0&2                         : Logitech USB Cordless Mouse
USB\VID_04F9&PID_0027\D5J857817                             : USB Printing Support
USBPRINT\BROTHERHL-2030_SERIES\6&49CBB41&0&USB001           : BrotherHL-2030 series
8 matching device(s) found.

2006-09-27 13:11:14 : <INIT> Logging of HWIDs complete.
2006-09-27 13:11:14 : <CRIT> Could not delete element from array!
2006-09-27 13:11:23 : <CLNP> Deleted the DriverPacks, which were located in 'H:\D'.
2006-09-27 13:11:23 : <CLNP> Deleted 'H:\DPsFnshr.ini'!
2006-09-27 13:11:23 : <CLNP> Deleted 'H:\devcon.exe'!
2006-09-27 13:11:23 : <CLNP> Deleted 'H:\makePNF.exe'!
2006-09-27 13:11:23 : <CLNP> Deleted 'H:\addUsepmtimer.exe'!
2006-09-27 13:11:23 : <CLNP> Deleted 'H:\ATICCC.ins'!
2006-09-27 13:11:23 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-09-27 13:11:23 : Program terminated.

  • From: Amherst, NY
  • Registered: 2006-05-27
  • Posts: 271

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Bâshrat the Sneaky wrote:

@RogueSpear: no, THAT is the error: that an element could not be deleted from an array. Probably because an incorrect index is specified, but that's the reason for adding all those debug statements, but unfortunately they're simply not working...

Ok, I was thinking this might be an error where you get a dialog box that shows where the code is choking.

RogueSpear's Website

  • Registered: 2006-07-24
  • Posts: 18

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

@Bâshrat - Could you post an ini file that you know works correctly?  In my case it's CPU,Chipset,LAN,WLAN,3rdparty (Modem,VMware), KTD, QC on.  I have also tried without QC and 3rdparty.  I would also be happy to try to sync up a time where we could do a VNC session from my PC so I can show you how I have it setup and what I do to get to the installable disc.

@Everybody - Is everyone that is having the problem using nlite and/or RyanVM packs?  Be specific. 

In my case I use both and do the RyanVM integration from within nlite 1.0.1.  I only take out a couple of things, messenger, msn.  I use a lot of the visual and shortcut tweaks.  Driver CABs get recompressed since I push the TCP limit up to 50.  I make a copy of the modified image then apply the DriverPacks to the copy.  Everytime I repeat the DriverPacks I do it off a another copy of the nlite/ryanvm image.  After integration I use Bink.nu's BCD program to build an ISO from the image tree.  I then do my VMware installs from the ISO or burn to CD for physical install on a PC.

-felipe

  • From: The Hague, NL
  • Registered: 2006-09-20
  • Posts: 5

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

I have seen the problem as well on VMWare.
I don't use nLite, but I do use the RyanVM updatepacks.
Bâshrat, do you need me to post my log and ini files? I've skimmed through them, and they seem about the same.

Ben.Hahlen's Website

  • Registered: 2006-07-24
  • Posts: 18

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Bump.  Still hoping for a resolution.

Ok..Tried it on a clean unmodified XP Pro file set, no nlite, no ryanvm.  Installed clean into VMware VM.  Same problem.  Same 'array' error.

I'm frustrated. 

-felipe

Last edited by felipegeek (2006-09-29 15:10:54)

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

I'm frustrated too. The Finisher has been in use for a while now, and now there are a few of people getting this error. A few, not all, not many, just a few. I will be testing it myself in detail today, though I have not yet been able to reproduce it.

Because it's such an unobvious, rather odd error, it's not easy to find the exact cause. Plus, as I've mentioned earlier, most people don't get this error, which makes it harder to find.

All I can tell you is that I'm working on it. This issue has currently my highest priority and I'm working very hard to get it fixed by today/tomorrow.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • [dk]
  • DriverPacks Magician
  • Offline
  • Registered: 2006-09-05
  • Posts: 44

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Bâshrat the Sneaky
thanx for info... and if you need more information to find cause - feel free to ask wink
I have some computers to execute installs and other tests

Mars 2025 - Online military-economic strategy game.

[dk]'s Website

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

I am rewriting this specific part so that it is more straightforward, and more resistant to possible flaws.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

'[dk wrote:

']hmm... I'll try to...
but DPsFnshr.ini is in "\$OEM$\$1" so it's copied automatically... and all other files are present in %systemdrive% folder
Here are contents of  Directory of D:\UCD\$OEM$\$1

05.09.2006  14:59    <DIR>          .
05.09.2006  14:59    <DIR>          ..
25.08.2006  04:03           181 791 addUsepmtimer.exe
05.09.2006  14:59                 0 ATICCC.ins
05.09.2006  14:58    <DIR>          D
25.08.2006  04:00            55 808 devcon.exe
25.08.2006  04:03           217 495 DPsFnshr.exe
06.09.2006  17:51            14 307 DPsFnshr.ini
01.09.2006  22:12    <DIR>          Install
25.08.2006  04:00            20 992 makePNF.exe

do you expect me to make entire integration process again?

Bashrat
add addusePMTIMER shows here

I think of RogueSpear
otoh, I seldom did method 1
when rogue mentioned it, (in a method 2 I believe), I looked too, and never found the file.

The answer was 42?
Kind regards, Jaak.
  • erik
  • DriverPacks newbie
  • Offline
  • Registered: 2006-10-02
  • Posts: 3

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

I'm having the exact same problem too (using method 2 with KTD, and I get the error message on screen and in the log).

Let me know how I can help with testing or what info I can post.

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

erik, I'm currently partially rewriting the Finisher to allow detailed debug logs and at teh same time I'm making the code easier to maintain. Currently you can't do much, except for just waiting or clicking the ads like a fool.

I will post the progress here, also when I've send the new Finisher out to the testing team.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • [dk]
  • DriverPacks Magician
  • Offline
  • Registered: 2006-09-05
  • Posts: 44

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Bâshrat the Sneaky
noticed a driverpack 6.09 - does it fix this issue?

Mars 2025 - Online military-economic strategy game.

[dk]'s Website

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

No. The partially rewritten Finisher is not yet finished (due to my accident with my hand), and it will first be tested by the testing team to ensure that it at least works equally good as it did previously (for them, that is, not for you).

I'm almost ready with it though, so probably I'll send it to the testers tonight.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • [dk]
  • DriverPacks Magician
  • Offline
  • Registered: 2006-09-05
  • Posts: 44

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

thanx for quick reply wink
recover faster - we need you smile

Mars 2025 - Online military-economic strategy game.

[dk]'s Website

  • fejker
  • DriverPacks newbie
  • Offline
  • From: Croatia
  • Registered: 2006-09-27
  • Posts: 3

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Hmmm, strange, with DriverPacks BASE 6.09 I don't have 'Couldn't delete element from array' error anymore! If DPFinisher is the same, what's been causing this error then?!

  • [dk]
  • DriverPacks Magician
  • Offline
  • Registered: 2006-09-05
  • Posts: 44

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Strange indeed, 'cos I've extracted DPsFnshr.7z and driverpacks along with .ini to %systemroot% (exactly as I did before), executed finisher and received the same error (Bâshrat the Sneaky - I know - I haven't been told to do this... I decided to try it myself wink )

It's clear, I'm talking about latest 6.09 BASE available...

Last edited by [dk] (2006-10-04 20:20:18)

Mars 2025 - Online military-economic strategy game.

[dk]'s Website

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

@fejker: did you download it BEFORE October 1, 19:30 GMT? Then it's normal. The wrong source got compiled, which includes the partially rewritten though not yet complete DriverPacks Finisher - it's not yet complete so it just doesn't work wink

@[dk]: you're right. The new DriverPacks Finisher works fine according to my testers so I'll be putting the new version online very soon wink

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

'[dk wrote:

']@Bâshrat the Sneaky - so you need any extra information I could provide?
And another question - could finisher be executed via cmdlines.txt before MUI is integrated?
(to get rid of possible conflicts with locale), although I've got following strings in winnt.sif:

[RegionalSettings]
    LanguageGroup=5,1
    SystemLocale=00000419
    UserLocale=00000419
    InputLocale=0409:00000409,0419:00000419

at DK
why are there two different inputlocal descriptors in string?

mine looks like this
[RegionalSettings]
    LanguageGroup=1
    Language=00000813
    SystemLocale=00000813
    UserLocale=00000813
    InputLocale=0813:00000813

The answer was 42?
Kind regards, Jaak.
  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Solved in DriverPack Sound B 6.10, which will be online in a couple of minutes.

I will leave this topic open for jtdoom's question to [dk], after that I'll close it.

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website

  • [dk]
  • DriverPacks Magician
  • Offline
  • Registered: 2006-09-05
  • Posts: 44

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

@jtdoom
well... it's for the reason - I want to use english input locale by default - and russian as second one...
though it also buggy - I duplicate this settings via regopts.txt applied via WPI (very last stage):

[RegionalSettings]
MUILanguage=0419
MUILanguage_DefaultUser=0419,00000419
LanguageGroup=5,1
SystemLocale=00000419
UserLocale=00000419
InputLocale=0409:00000409,0419:00000419

it's along with applying some registry tweaks for codepages...

Mars 2025 - Online military-economic strategy game.

[dk]'s Website

  • [dk]
  • DriverPacks Magician
  • Offline
  • Registered: 2006-09-05
  • Posts: 44

Re: [SOLVED BUG #266] [Finisher] Critical error: "Could not delete element

Bâshrat the Sneaky
well... it seems to be ok - no errors in log
you rock! wink

the only one question to get myself confident - "C:\Windows\DriverPacks\D\D\..." - is it normal path to driverpacks?

Last edited by [dk] (2006-10-06 00:42:59)

Mars 2025 - Online military-economic strategy game.

[dk]'s Website