Index: openacs-4/packages/acs-bootstrap-installer/tcl/20-db-bootstrap-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-bootstrap-installer/tcl/20-db-bootstrap-procs.tcl,v
diff -u -r1.1 -r1.2
--- openacs-4/packages/acs-bootstrap-installer/tcl/20-db-bootstrap-procs.tcl	12 Apr 2001 16:58:18 -0000	1.1
+++ openacs-4/packages/acs-bootstrap-installer/tcl/20-db-bootstrap-procs.tcl	21 Nov 2001 01:26:11 -0000	1.2
@@ -34,7 +34,8 @@
     #    where no AvailablePool parameters exist, as in that case the ACS
     #    slurps up all pools.  I expect mixed db environments to be more common
     #    within the OpenACS community, though, so we should do a better job of
-    #    checking.
+    #    checking.  This will especially be true of users migrating from an
+    #    [Open]ACS 3.x site or ACS 4.x classic site.
     #
     # 2. There was no checking to make sure that *all* pools are correctly
     #    configured.  Even in an Oracle-only environment one could easy mistype a
@@ -74,7 +75,7 @@
 
     if { [string length $the_set] > 0 } {
         for {set i 0} {$i < [ns_set size $the_set]} {incr i} {
-            if { [ns_set key $the_set $i] ==  "AvailablePool" } {
+            if { [string tolower [ns_set key $the_set $i]] ==  "availablepool" } {
                 lappend pools [ns_set value $the_set $i]
             }
         }